arch-lens-development
Skill1 starsChanged 8 months agoMITView on GitHub
Create Development architecture diagram showing project structure, build tools, and quality gates. Development lens answering "How is it built and tested?
In this repository59 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- arch-lens-c4-containerSkill
- arch-lens-concurrencySkill
- arch-lens-data-lineageSkill
- arch-lens-deploymentSkill
- arch-lens-error-resilienceSkill
- arch-lens-module-dependencySkill
- arch-lens-operationalSkill
- arch-lens-process-flowSkill
- arch-lens-repository-accessSkill
- arch-lens-scenariosSkill
- arch-lens-securitySkill
- arch-lens-state-lifecycleSkill
- audit-archSkill
- audit-bugsSkill
- audit-cohesionSkill
- audit-defense-standardsSkill
- audit-frictionSkill
- audit-implSkill
- audit-testsSkill
- design-guardsSkill
- dry-walkthroughSkill
- elaborate-phaseSkill
- exp-lens-benchmark-representativenessSkill
- exp-lens-causal-assumptionsSkill
- exp-lens-comparator-constructionSkill
- exp-lens-error-budgetSkill
- exp-lens-estimand-claritySkill
- exp-lens-exploratory-confirmatorySkill
- exp-lens-fair-comparisonSkill
- exp-lens-governance-riskSkill
- exp-lens-iterative-learningSkill
- exp-lens-measurement-validitySkill
- exp-lens-pipeline-integritySkill
- exp-lens-randomization-blockingSkill
- exp-lens-reproducibility-artifactsSkill
- exp-lens-sensitivity-robustnessSkill
- exp-lens-severity-testingSkill
- exp-lens-unit-interferenceSkill
- exp-lens-validity-threatsSkill
- exp-lens-variance-stabilitySkill
- id-slopSkill
- implement-worktreeSkill
- investigateSkill
- make-arch-diagSkill
- make-experiment-diagSkill
- make-groupsSkill
- make-planSkill
- make-reqSkill
- make-scenariosSkill
- mermaidSkill
- plan-arcSkill
- rectifySkill
- review-approachSkill
- update-architectureSkill
- update-reqsSkill
- update-specsSkill
- verify-diagSkill
- verify-proposed-diagSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 11 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 36
Document test framework setup
- Very specific: line 38
BEFORE creating any diagram, LOAD the /mermaid skill using the Skill tool - this is MANDATORY
- Distinctive: line 51
Look for: build configs, package definitions, project layout
- Distinctive: line 56
Look for: build config files, makefiles, task runners, package managers
- Distinctive: line 61
Look for: linter configs, formatter configs, pre-commit hooks, code quality tools
- Distinctive: line 66
Look for: type checker configs, static analysis tools
- Distinctive: line 71
Look for: test configs, test directories, test runners, test fixtures
- Distinctive: line 76
Look for: CI/CD configs, workflow definitions, pipeline configs
- Distinctive: line 81
Look for: entry point definitions, command definitions, binary files
- Distinctive: line 85
Document the code quality pipeline:
- Distinctive: line 121
Test Framework (test runner, etc)
- Very specific: line 137
Write the diagram to: temp/arch-lens-development/arch_diag_development_{YYYY-MM-DD_HHMMSS}.md
- Distinctive: line 257
Before creating the diagram, verify:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Development Architecture Lens
Cognitive Mode: Development Primary Question: "How is it built and tested?" Focus: Project Structure, Build Tools, Quality Gates, Test Framework
When to Use
- Need to understand developer experience
- Documenting build and test infrastructure
- Analyzing code quality gates
- User invokes
/arch-lens-developmentor/make-arch-diag development
Critical Constraints
NEVER:
- Modify any source code files
- Include runtime architecture details
- Show business logic
ALWAYS:
- Focus on BUILD and TEST infrastructure
- Show quality gate pipeline
- Document test framework setup
- Include entry points
- BEFORE creating any diagram, LOAD the
/mermaidskill using the Skill tool - this is MANDATORY
Analysis Workflow
Step 1: Launch Parallel Exploration Subagents
Spawn Explore subagents to investigate:
Project Structure
- Find top-level directory organization
- Identify module/package boundaries
- Look for: build configs, package definitions, project layout
Build Tooling
- Find build configuration
- Identify package manager and build backend
- Look for: build config files, makefiles, task runners, package managers
Linting & Formatting
- Find code quality tools
- Identify pre-commit hooks
- Look for: linter configs, formatter configs, pre-commit hooks, code quality tools
Type Checking
- Find type checking configuration
- Identify strictness level
- Look for: type checker configs, static analysis tools
Test Framework
- Find test configuration
- Identify test patterns and fixtures
- Look for: test configs, test directories, test runners, test fixtures
CI/CD (if present)
- Find CI configuration
- Identify workflow stages
- Look for: CI/CD configs, workflow definitions, pipeline configs
Entry Points
- Find CLI entry points
- Identify console scripts
- Look for: entry point definitions, command definitions, binary files
Step 2: Map Quality Pipeline
Document the code quality pipeline:
Code -> Format -> Lint -> Type Check -> Test -> CommitCRITICAL - Analyze Read/Write Direction: For EVERY build/test component:
- Inputs (reads): What files/config does this tool READ?
- Outputs (writes): What does this tool WRITE (reports, modified files)?
- Side effects: Does it modify source files or just report?
Distinguish:
- Tools that READ and MODIFY code (formatters)
- Tools that READ and REPORT only (linters, type checkers)
- Tools that READ code and WRITE artifacts (test output files)
- Config files (READ by tools, not written by build process)
Step 3: Count Project Metrics
| Metric | Value |
| Source Files | N |
| Test Files | N |
| Dependencies | N |
| Entry Points | N |
Step 4: Create the Diagram
Use flowchart with:
Direction: TB for pipeline flow
Subgraphs:
- Project Structure (directories)
- Build Tools (packaging)
- Quality Gates (linting, types)
- Test Framework (test runner, etc)
- Entry Points (CLI commands)
Node Styling:
cliclass: Project structure, directoriesphaseclass: Build configurationdetectorclass: Quality gates (linting, typing)handlerclass: Test frameworkoutputclass: Entry points, outputs
Show Pipeline Flow:
- Code through quality gates
- Build to entry points
Step 5: Write Output
Write the diagram to: temp/arch-lens-development/arch_diag_development_{YYYY-MM-DD_HHMMSS}.md
Output Template
# Development Diagram: {Project Name}
**Lens:** Development (Build & Test)
**Question:** How is it built and tested?
**Date:** {YYYY-MM-DD}
**Scope:** {What was analyzed}
## Project Metrics
| Metric | Value |
|--------|-------|
| Source Directories | {count} |
| Test Files | {count} |
| Dependencies | {count} |
| Entry Points | {count} |
## Development Diagram
```mermaid
%%{init: {'flowchart': {'nodeSpacing': 50, 'rankSpacing': 60, 'curve': 'basis'}}}%%
flowchart TB
%% CLASS DEFINITIONS %%
classDef cli fill:#1a237e,stroke:#7986cb,stroke-width:2px,color:#fff;
classDef stateNode fill:#004d40,stroke:#4db6ac,stroke-width:2px,color:#fff;
classDef handler fill:#e65100,stroke:#ffb74d,stroke-width:2px,color:#fff;
classDef phase fill:#6a1b9a,stroke:#ba68c8,stroke-width:2px,color:#fff;
classDef output fill:#00695c,stroke:#4db6ac,stroke-width:2px,color:#fff;
classDef detector fill:#b71c1c,stroke:#ef5350,stroke-width:2px,color:#fff;
subgraph Structure ["PROJECT STRUCTURE"]
direction TB
SRC["src/<br/>━━━━━━━━━━<br/>Source code"]
TESTS["tests/<br/>━━━━━━━━━━<br/>Test suite"]
end
subgraph Build ["BUILD TOOLING"]
direction TB
CONFIG["Build Config<br/>━━━━━━━━━━<br/>Build system"]
TASKFILE["Task Runner<br/>━━━━━━━━━━<br/>Task automation"]
end
subgraph Quality ["CODE QUALITY GATES"]
direction TB
FORMAT["Formatter<br/>━━━━━━━━━━<br/>Code style"]
LINT["Linter<br/>━━━━━━━━━━<br/>Code quality"]
TYPES["Type Checker<br/>━━━━━━━━━━<br/>Static analysis"]
end
subgraph Testing ["TEST FRAMEWORK"]
direction TB
TESTRUN["Test Runner<br/>━━━━━━━━━━<br/>Test execution"]
FIXTURES["Fixtures<br/>━━━━━━━━━━<br/>Test setup"]
end
subgraph EntryPoints ["ENTRY POINTS"]
direction LR
EP1["cli-command"]
end
%% FLOW %%
SRC --> CONFIG
TESTS --> CONFIG
CONFIG --> TASKFILE
CONFIG --> FORMAT
FORMAT --> LINT
LINT --> TYPES
TYPES --> TESTRUN
TESTRUN --> FIXTURES
CONFIG --> EP1
%% CLASS ASSIGNMENTS %%
class SRC,TESTS cli;
class CONFIG,TASKFILE phase;
class FORMAT,LINT,TYPES detector;
class TESTRUN,FIXTURES handler;
class EP1 output;Color Legend:
| Color | Category | Description |
| Dark Blue | Structure | Project directories |
| Purple | Build | Configuration and automation |
| Red | Quality | Linters and type checkers |
| Orange | Testing | Test framework and fixtures |
| Dark Teal | Entry Points | CLI commands |
Development Workflow
Code -> format -> lint -> type-check -> test -> commitPre-commit Hooks
| Hook | Purpose |
| {hook} | {purpose} |
Entry Points
| Command | Module | Purpose |
| {command} | {module} | {purpose} |
---
## Pre-Diagram Checklist
Before creating the diagram, verify:
- [ ] LOADED `/mermaid` skill using the Skill tool
- [ ] Using ONLY classDef styles from the mermaid skill (no invented colors)
- [ ] Diagram will include a color legend table
---
## Related Skills
- `/make-arch-diag` - Parent skill for lens selection
- `/mermaid` - MUST BE LOADED before creating diagramDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

