Individual skill
architect
Settle data shapes, ownership, boundaries, and interfaces before code crosses a function/module boundary. Use for non-trivial design work.
skills/architect/SKILL.md
Source commit 79595c97d47b5400034fb985e67f1a00389a81af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 21
- Repository last updated
- Nov 1, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- codex Repository topic
- coding-agents Repository topic
- cursor Repository topic
- pstack Repository topic
- cline Repository topic
- copilot Repository topic
- gemini Repository topic
- design Derived category
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 894 bytes
Read excerpt
# Architect
Read the caller first. Architecture starts from use, not from an isolated abstraction.
1. Name the domain data shape and invariants.
2. Map ownership and lifecycle. For concurrency, identify what is truly shared before proposing synchronization.
3. Draft 2-3 boundary shapes when the decision is contested. If `delegate` is available, assign independent designs; otherwise keep alternatives explicit and sequential.
4. Compare on reader load, invalid states, migration cost, idempotence, testability, and fit with existing architecture.
5. Select the smallest coherent shape and write the caller-facing signature/contract before implementation.
6. Use `interrogate` for high-risk or contested decisions.