learn-architecture
Skill2 starsChanged 19 days agoApache-2.0View on GitHub
Deep scan of project structure to update architecture knowledge. Uses semantic code search for API, model, error, and test patterns. Use to bootstrap or refresh project knowledge.
In this repository124 other files it gives its agents.
- add-projectSkill
- ansible-configure-vmSkill
- api-smoke-testSkill
- appinterface-checkSkill
- attach-session-to-jiraSkill
- aws-rds-debugSkill
- beerSkill
- bootstrap-all-knowledgeSkill
- bootstrap-knowledgeSkill
- build-persona-styleSkill
- cancel-pipelineSkill
- cert-checkSkill
- check-ci-healthSkill
- check-integration-testsSkill
- check-mr-feedbackSkill
- check-my-prsSkill
- check-secretsSkill
- ci-retrySkill
- cleanup-branchesSkill
- cleanup-stale-executionsSkill
- clone-jira-issueSkill
- close-issueSkill
- close-mrSkill
- cloud-inventorySkill
- coffeeSkill
- compare-optionsSkill
- create-jira-issueSkill
- create-mrSkill
- create-slide-deckSkill
- data-migration-verifySkill
- debug-local-dbSkill
- debug-prodSkill
- deploy-to-ephemeralSkill
- dev-workflow-orchestratorSkill
- discovered-work-summarySkill
- edit-slide-deckSkill
- email-digestSkill
- environment-overviewSkill
- explain-codeSkill
- export-presentationSkill
- extend-ephemeralSkill
- find-similar-codeSkill
- gather-contextSkill
- gdrive-researchSkill
- gke-cluster-opsSkill
- hello-worldSkill
- hotfixSkill
- inscope-researchSkill
- investigate-alertSkill
- investigate-service-issuesSkill
- investigate-slack-alertSkill
- jira-hygiene-allSkill
- jira-hygieneSkill
- knowledge-refreshSkill
- konflux-statusSkill
- learn-patternSkill
- list-presentationsSkill
- local-build-testSkill
- local-dev-environmentSkill
- manage-local-servicesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 32
Read pyproject.toml, requirements.txt, package.json
- Very specific: line 40
If focus: code_search("{focus} implementation pattern", project, limit=10) → focus_patterns
- Very specific: line 54
If "index not found": learn_tool_fix("code_search", "index not found", "Vector index not created", "Run skill_run('bootstrap_knowledge')")
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Learn Architecture
Scans directory structure, dependencies, and semantic patterns to update project knowledge.
Inputs
| Input | Type | Default | Purpose |
project | string | auto | Project from config (auto from cwd) |
persona | string | current | Persona to update |
focus | string | - | Area to focus (e.g., "api", "tests", "models") |
use_vector_search | bool | true | Use semantic search for pattern discovery |
Workflow
1. Check Known Issues
check_known_issues(tool_name="code_search", error_text="")
2. Detect Project & Persona
- Infer project from cwd via config; default persona "developer"
3. Scan Directory Structure
- Walk project path (max 3 levels), skip node_modules, pycache, venv
- Build tree of key dirs: src, lib, app, api, core, services, models, tests, etc.
4. Analyze Dependencies
- Read pyproject.toml, requirements.txt, package.json
- Extract top dependencies
5. Semantic Code Search (if use_vector_search)
code_search("API endpoint route handler request response", project, limit=10)→ api_patternscode_search("class model schema database table field", project, limit=10)→ model_patternscode_search("exception error handling try except raise", project, limit=10)→ error_patternscode_search("test fixture mock assert pytest unittest", project, limit=10)→ test_patterns- If focus:
code_search("{focus} implementation pattern", project, limit=10)→ focus_patterns
6. Update Knowledge
knowledge_update(project, persona, section="architecture.key_modules", content=modules_list)knowledge_update(project, persona, section="architecture.dependencies", content=dependencies)
7. Build Result
Output markdown with:
- Key modules found
- Dependencies list
- Patterns discovered (API, models, errors, tests)
- Focus area results if specified
8. Error Handling
- If "index not found":
learn_tool_fix("code_search", "index not found", "Vector index not created", "Run skill_run('bootstrap_knowledge')")
9. Log
memory_session_log("Learned architecture for {project}", "Persona: {persona}")
Key MCP Tools
code_search— semantic pattern discoveryknowledge_update— write architecture to knowledgecheck_known_issues,learn_tool_fix— error handlingmemory_session_log— session logging
Does 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.

