3-identifying-architecture
Third step in building instruction context for codebase
npx skills add majiayu000/claude-skill-registry --skill 3-identifying-architecture-bitovi-context-generation-m --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
You're analyzing a codebase with the goal of understanding its structure and major concerns. The tech stack is summarized in ./{output-folder}/1-techstack.md. Categorized files are listed in ./{output-folder}/2-file-categorization.json. > This task may take some time — that is expected and acceptable. > Do **not** skip files or produce partial results due to time or complexity. Accuracy and completeness are **mission-critical**. > You are permitted to take as long as necessary to: > > - Review every relevant file > - Extract actual patterns and conventions > - Produce complete, high-fidelity output > If a file is listed in ./{output-folder}/2-file-categorization.json or is part of a relevant domain, it **must** be included in your analysis. > Do not optimize for speed or brevity. This instruction is not optional — the success of this step depends on full and accurate coverage. Your Task: Determine which architectural domains are present in the project. Consider: - File structure and naming patterns - Framework conventions - Imports and usage patterns - Configuration files - Common architectural markers (e.g., components/, routes/, handlers/, services/, cli/, etc.) **Critical Analys
What does the 3-identifying-architecture skill do?
Third step in building instruction context for codebase
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill 3-identifying-architecture-bitovi-context-generation-m --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.