architect
An agent skill by cursor, from cursor/plugins. Tags: architecture, design, development, planning, system-design.
What it does
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add cursor/plugins --skill architect
Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/cursor/plugins
cp -r plugins/pstack/skills/architect ~/.claude/skills/architect
Safety box score
Grade B, low risk: 16 of 100 risk points, rated 2026-09-25. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This is a workflow-only architecture skill that reads the repository, runs parallel design exploration, and can then drive code edits in the project. It does not itself touch network, secrets, or privileges, but it does default to moving from planning into implementation without a human checkpoint, so the main risk is broad repository churn.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 0 (none) | No shell commands, script bodies, or code-eval machinery appear in the files; it only says to "run the how skill" and "run the arena skill." |
| Network access | 0 (none) | The skill contains no URL fetches, API calls, or remote data transfer commands. |
| Filesystem reach | 1 (low) | It is intended to edit repository files during Phase D, e.g. "Replace `not implemented` bodies with code" and may "throw the sketch out" and redesign, but it stays within the project/worktree. |
| Secrets & credentials | 0 (none) | There is no mention of tokens, keys, passwords, `.env` files, browser sessions, or other credential stores. |
| Privilege & persistence | 0 (none) | The files do not request sudo, global installs, services, or OS/shell configuration changes. |
| Instruction hijack surface | 1 (low) | It explicitly says "Default: proceed directly to implementation. No human checkpoint," which is a skip-confirmation workflow directive, though not hidden or remote-sourced. |
| Irreversible actions | 2 (moderate) | The skill can move from design into implementation and even scrap/rewrite the architecture on its own, as in "Default: proceed directly to implementation" and "throw the sketch out." |
| Transparency | 0 (none) | All shipped files are plain markdown; there are no binaries, base64 blobs, generated installers, or unpinned external downloads. |
Before installing
- Read `SKILL.md` and decide whether you want the default no-checkpoint flow or the opt-in pause.
- Use a disposable branch or worktree if you expect the `Scrap` phase to rewrite substantial code.
- Expect it to invoke other skills and produce multiple candidate designs before implementation.
Rated 2026-09-25 by an automated review of 4 files from the skill's repository.
Source
- Repository
- cursor/plugins (all skills from this repository)
- Path
- pstack/skills/architect/SKILL.md
- Branch
- main
- Collection
- cursor
- Updated
- 2026-09-23
Related skills
- principle-foundational-thinking — Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share.
- principle-model-the-domain — Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files.
- expo-project-structure — Framework (OSS). Folder structure for a new Expo app.
- how — Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live".
- principle-boundary-discipline — Apply when wiring validation, error handling, or framework adapters.
- principle-exhaust-the-design-space — Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase.