Decide, review, or document app structure — folder responsibilities, module boundaries, and conventions.
SkillScore91Maintained
Automatic
◆Coding pack
Last verified 8/3/2026
What it changes
Passed 20 of 22 test cases with the skill, and 15 of 22 without it.
Without skill68%
With skill91%
Checks it passed that the model alone missed
The mapping assigns state management to /store.
The plan specifies updating imports after each batch of moved files.
The roadmap specifies updating all import statements after relocating each batch of files.
and 3 more in the full report
5 fixed15 passed either way2 still failing0 broke
Pass-rate lift
+23 pp
Tokens
+3%
Agent turns
0%
Response time
-41%
Model gemini-3.6-flashMeasured 8/3/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
We are setting up a brand-new Next.js application, and our team needs a formal blueprint for how to organize our codebase before writing any core features. Please examine our framework requirements and construct a structured directory blueprint that categorizes our route handlers, UI components, helper functions, global state management, and TypeScript definitions. Include brief architectural notes explaining the purpose of each top-level area so future contributors follow consistent guidelines.
What was checked, without and with the skill
Checked
Without skill
With skill
The blueprint places helper functions in /lib rather than creating a separate /utils folder.
Missed
Passed
The top-level structure uses /app for routes.
Passed
Passed
case-04 · gemini-3.6-flash · 8/3/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md71 linessingle file
Architecture Planning Skill
Purpose
Establish or review the structural rules of the project — where code lives, how layers interact, and what conventions apply — so the codebase stays organized and predictable as it grows.
When to Use
Starting a new project or a new major area with no established convention yet.
A new feature doesn't fit any existing folder/module pattern.
Explicitly asked to review, document, or improve the architecture.
The task is specifically scoped as architecture setup, restructuring, or migration.
When Not to Use
Routine feature work that fits the existing structure — just follow the convention (see Understand the Project Skill).
Small one-off files that clearly belong in an existing folder by existing rules.
Required Inputs
Current project structure (from Understand the Project Skill).
The framework in use and its routing/structure conventions.
The specific architectural question or gap driving this task.
Assumptions
If the project has an established structure, it takes precedence over the default rule of thumb.
Architecture changes are higher-risk and broad — they affect many files and future work.
Step-by-Step Workflow
Confirm the framework's structural conventions (e.g. Next.js App Router file conventions, Expo Router file-based routing, Vite project layout).
Inventory current structure: list top-level folders and what currently lives in each; note any inconsistencies.
Identify the gap or question: e.g. "where should shared form validation logic live?" or "this feature needs a new top-level area — where does it go?"
Apply the default rule of thumb as a baseline when no stronger convention exists:
/app = routes and screens
/components = UI
/lib = helper logic
/services = API/business calls
/db = database
/hooks = React logic
/store = global state
/types = TypeScript types
/styles = global CSS
/public = images and static files
Decide placement based on responsibility, not convenience — ask "where would a future developer look for this?"