Note: This English text was translated and edited with LLM assistance. If anything reads awkwardly, please check the Korean version or open an issue.
structure-first is a skill for making the Primary Flow of code readable first.
It keeps boundaries minimal, pushes detail downward, and favors contract-focused tests.
The goal is to reduce change radius and side effects during complex changes.
Spec: agentskills.io | License: MIT | Agents: Codex, Claude Code
The optional structure-first-docs skill applies the same philosophy to engineering documents such as design docs, plans, and runbooks.
Install
npx skills add perhapsspy/structure-firstTry It
$structure-first implement this feature
- When state/condition branching makes top-down reading hard
- When AI edits frequently create side effects
- When tests break because they follow implementation details too closely
Start with structure-first first, then add companion skills only when needed.
- Fast install via skills.sh:
npx skills add perhapsspy/structure-first - Local install: copy
skills/structure-firstinto your agent's local skills directory
structure-first-docs: optional companion skill that applies the same structural philosophy to document writing/review
# For implementation
$structure-first implement this feature
# For improving existing code
$structure-first analyze this code and propose improvements
# To apply the same philosophy to docs
$structure-first-docs write/review this design doc
- Detailed skill rules: English | Korean
- Docs companion skill: English | Korean
- Dev story: English | Korean
- Background notes: English | Korean
structure-first: organize code so the primary success path reads top-downproject-context: keep working context in the repo so later sessions can resume quickly
