[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CCZWXQACZNWHEMSRJZBSD7":3,"skill-same:01M6CCZWXQACZNWHEMSRJZBSD7":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":14,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6CCZWXQACZNWHEMSRJZBSD7","code-architecture",null,"Architectural analysis workflow using Serena symbols and Brain memory. Use when analyzing project structure, documenting architecture, creating component entities, or building knowledge graphs from code.","loriensleafs\u002Fbrain","loriensleafs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F315385?v=4","01M6CCYZETMCJPTHNS258YRCBC","Peter Kloss","01M6CCYZK25T8516A39S9PCJT7",0,"MIT","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fcode-architecture\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40],"architecture","code","code architecture","memory","workflow","component","project structure","analyzing","analysis","architect","knowledge","use","2026-11-10 10:12:30",false,"---\nname: code-architecture\ndescription: Architectural analysis workflow using Serena symbols and Brain memory. Use when analyzing project structure, documenting architecture, creating component entities, or building knowledge graphs from code.\nlicense: MIT\nmetadata:\n  version: 1.0.0\nmodel: claude-opus-4-5\nagents: [analyst, architect]\n---\n\n# Code Architecture Analysis\n\nThis skill guides systematic architectural analysis using Serena's symbol-level understanding, with optional persistence to Brain's knowledge graph.\n\n## Triggers\n\n| Trigger Phrase | Operation |\n|----------------|-----------|\n| `analyze the architecture of this project` | Full 6-phase analysis workflow |\n| `map out the codebase structure` | Phase 1-3 discovery and component mapping |\n| `trace dependencies for this component` | Phase 4 dependency tracing |\n| `create architecture memories` | Phase 5-6 memory and entity creation |\n| `what components does this project have` | Phase 3 core component mapping |\n\n---\n\n## When to Use This Skill\n\nUse this skill when:\n\n- Analyzing a new codebase before implementing changes\n- Documenting existing architecture for a project\n- Creating component entities and relationships in Brain memory\n- Understanding dependencies and call hierarchies\n- Building a knowledge graph from code structure\n\nUse [code-symbols](..\u002Fcode-symbols\u002FSKILL.md) instead when:\n\n- Quick symbol lookup without memory persistence\n- Finding a specific class or method definition\n- Tracing references for a single symbol\n\n## Analysis Workflow\n\n### Phase 1: Project Structure Discovery\n\nUnderstand the high-level layout:\n\n```python\n# Get directory structure\nmcp__plugin_serena_serena__list_dir({\n  \"relative_path\": \".\",\n  \"recursive\": false\n})\n\n# Identify key directories (src\u002F, app\u002F, lib\u002F, etc.)\nmcp__plugin_serena_serena__list_dir({\n  \"relative_path\": \"src\",\n  \"recursive\": true\n})\n```\n\n**Goal**: Identify entry points, main modules, and organizational patterns.\n\n### Phase 2: Entry Point Analysis\n\nFind the application entry points:\n\n```python\n# Look for main\u002Fapp files\nmcp__plugin_serena_serena__search_for_pattern({\n  \"substring_pattern\": \"if __name__.*==.*__main__|def main\\\\(|app\\\\s*=\\\\s*FastAPI|createApp\",\n  \"restrict_search_to_code_files\": true\n})\n\n# Get symbols from entry file\nmcp__plugin_serena_serena__get_symbols_overview({\n  \"relative_path\": \"src\u002Fmain.py\",\n  \"depth\": 1\n})\n```\n\n### Phase 3: Core Component Mapping\n\nIdentify and analyze major components:\n\n```python\n# Find all service\u002Fcontroller\u002Fmodel classes\nmcp__plugin_serena_serena__find_symbol({\n  \"name_path_pattern\": \"Service\",\n  \"substring_matching\": true,\n  \"include_kinds\": [5],  # Class only\n  \"depth\": 1\n})\n\n# For each major component, get full structure\nmcp__plugin_serena_serena__find_symbol({\n  \"name_path_pattern\": \"AuthService\",\n  \"include_body\": false,\n  \"depth\": 1  # Get methods\n})\n```\n\n### Phase 4: Dependency Tracing\n\nUnderstand how components connect:\n\n```python\n# Find who uses AuthService\nmcp__plugin_serena_serena__find_referencing_symbols({\n  \"name_path\": \"AuthService\",\n  \"relative_path\": \"src\u002Fservices\u002Fauth.py\"\n})\n\n# Find what AuthService depends on\nmcp__plugin_serena_serena__find_symbol({\n  \"name_path_pattern\": \"AuthService\u002F__init__\",\n  \"include_body\": true\n})\n```\n\n### Phase 5: Create Architectural Memories (Optional)\n\nStore findings in Brain memory notes:\n\n```python\n# Write a Brain memory note for architectural insight\nmcp__plugin____brain__write_note({\n  \"title\": \"ANALYSIS-001 AuthService Architecture\",\n  \"content\": \"---\\ntitle: ANALYSIS-001 AuthService Architecture\\ntype: analysis\\ntags: [auth, jwt, architecture]\\n---\\n\\n# ANALYSIS-001 AuthService Architecture\\n\\n## Observations\\n\\n- [fact] AuthService handles JWT validation, user sessions, and OAuth flows #auth\\n- [fact] Dependencies: UserRepository, TokenService, CacheService #dependencies\\n- [fact] Used by all API endpoints via middleware #integration\\n\\n## Relations\\n\\n- part_of [[Project Architecture]]\\n- depends_on [[UserRepository]]\\n- depends_on [[TokenService]]\",\n  \"folder\": \"analysis\"\n})\n```\n\n### Phase 6: Entity Graph Creation (Optional)\n\nCreate Brain memory notes for major components with relations:\n\n```python\n# Create component note with relations\nmcp__plugin____brain__write_note({\n  \"title\": \"ANALYSIS-002 Component Graph\",\n  \"content\": \"---\\ntitle: ANALYSIS-002 Component Graph\\ntype: analysis\\ntags: [components, graph, architecture]\\n---\\n\\n# ANALYSIS-002 Component Graph\\n\\n## Observations\\n\\n- [fact] AuthService is central auth component #service\\n- [fact] UserRepository handles data access #repository\\n- [decision] Components linked via dependency injection #pattern\\n\\n## Relations\\n\\n- relates_to [[ANALYSIS-001 AuthService Architecture]]\\n- part_of [[Project Architecture]]\",\n  \"folder\": \"analysis\"\n})\n```\n\n## Relationship Types\n\nStandard relationship types for architecture:\n\n| Type | Use For |\n|------|---------|\n| `uses` | General usage (A uses B) |\n| `depends_on` | Dependency (A requires B) |\n| `calls` | Direct function\u002Fmethod calls |\n| `extends` | Class inheritance |\n| `implements` | Interface implementation |\n| `connects_to` | External connections (DB, API) |\n| `contains` | Composition (A contains B) |\n\n## Entity Types for Architecture\n\n| Type | Use For |\n|------|---------|\n| `Service` | Business logic services |\n| `Repository` | Data access layer |\n| `Controller` | Request handlers |\n| `Middleware` | Request\u002Fresponse processing |\n| `Model` | Data models\u002Fentities |\n| `Library` | External dependencies |\n| `Framework` | Framework components |\n\n## Example: FastAPI Project Analysis\n\n```python\n# 1. Find routers\nmcp__plugin_serena_serena__search_for_pattern({\n  \"substring_pattern\": \"APIRouter\\\\(\\\\)|router\\\\s*=\",\n  \"restrict_search_to_code_files\": true\n})\n\n# 2. Analyze router structure\nmcp__plugin_serena_serena__get_symbols_overview({\n  \"relative_path\": \"src\u002Frouters\u002Fusers.py\",\n  \"depth\": 1\n})\n\n# 3. Find dependency injection\nmcp__plugin_serena_serena__search_for_pattern({\n  \"substring_pattern\": \"Depends\\\\(\",\n  \"restrict_search_to_code_files\": true,\n  \"context_lines_before\": 1,\n  \"context_lines_after\": 1\n})\n\n# 4. Trace service dependencies\nmcp__plugin_serena_serena__find_referencing_symbols({\n  \"name_path\": \"get_current_user\",\n  \"relative_path\": \"src\u002Fdependencies\u002Fauth.py\"\n})\n\n# 5. Create architecture Brain memory note\nmcp__plugin____brain__write_note({\n  \"title\": \"ANALYSIS-003 FastAPI App Structure\",\n  \"content\": \"---\\ntitle: ANALYSIS-003 FastAPI App Structure\\ntype: analysis\\ntags: [fastapi, router, dependency-injection]\\n---\\n\\n# ANALYSIS-003 FastAPI App Structure\\n\\n## Observations\\n\\n- [fact] App uses router-based organization with dependency injection #architecture\\n- [fact] Routers: \u002Fusers, \u002Fauth, \u002Fproducts #routing\\n- [fact] Dependencies: get_current_user, get_db #dependencies\\n- [fact] All routes require auth except \u002Fauth\u002Flogin #security\\n\\n## Relations\\n\\n- part_of [[Project Architecture]]\",\n  \"folder\": \"analysis\"\n})\n```\n\n## Analysis Checklist\n\n- [ ] Directory structure mapped\n- [ ] Entry points identified\n- [ ] Major components catalogued\n- [ ] Dependencies traced\n- [ ] External connections documented\n- [ ] Key patterns identified\n- [ ] Brain memory notes created for insights\n- [ ] Component notes created (if applicable)\n- [ ] Relationships mapped (if applicable)\n\n## Anti-Patterns\n\n| Avoid | Why | Instead |\n|-------|-----|---------|\n| Analyzing every class as a component | Creates noise in knowledge graph | Focus on major architectural components only |\n| Reading full source before overview | Wastes tokens on unneeded code | Start with get_symbols_overview, read selectively |\n| Creating notes without relations | Notes lack context without linked knowledge | Create notes with observations and relations |\n| Skipping dependency tracing | Misses critical coupling relationships | Always run Phase 4 for components you create notes for |\n| Documenting WHAT without WHY | Notes become stale quickly | Focus notes on rationale and trade-offs |\n\n---\n\n## Verification\n\nAfter architectural analysis:\n\n- [ ] Directory structure mapped (Phase 1)\n- [ ] Entry points identified (Phase 2)\n- [ ] Major components catalogued (Phase 3)\n- [ ] Dependencies traced for key components (Phase 4)\n- [ ] Brain memory notes created for insights\n- [ ] Notes linked via relations\n\n---\n\n## Tips\n\n1. **Work incrementally** - Don't try to analyze everything at once\n2. **Focus on interfaces** - Public methods\u002FAPIs matter more than internals\n3. **Document decisions** - Create notes for WHY, not just WHAT\n4. **Use notes sparingly** - Only major components, not every class\n5. **Link across projects** - Architecture patterns often apply elsewhere\n","# Code Architecture Analysis\n\nThis skill guides systematic architectural analysis using Serena's symbol-level understanding, with optional persistence to Brain's knowledge graph.\n\n## Triggers\n\n| Trigger Phrase | Operation |\n|----------------|-----------|\n| `analyze the architecture of this project` | Full 6-phase analysis workflow |\n| `map out the codebase structure` | Phase 1-3 discovery and component mapping |\n| `trace dependencies for this component` | Phase 4 dependency tracing |\n| `create architecture memories` | Phase 5-6 memory and entity creation |\n| `what components does this project have` | Phase 3 core component mapping |\n\n---\n\n## When to Use This Skill\n\nUse this skill when:\n\n- Analyzing a new codebase before implementing changes\n- Documenting existing architecture for a project\n- Creating component entities and relationships in Brain memory\n- Understanding dependencies and call hierarchies\n- Building a knowledge graph from code structure\n\nUse [code-symbols](..\u002Fcode-symbols\u002FSKILL.md) instead when:\n\n- Quick symbol lookup without memory persistence\n- Finding a specific class or method definition\n- Tracing references for a single symbol\n\n## Analysis Workflow\n\n### Phase 1: Project Structure Discovery\n\nUnderstand the high-level layout:\n\n```python\n# Get directory structure\nmcp__plugin_serena_serena__list_dir({\n  \"relative_path\": \".\",\n  \"recursive\": false\n})\n\n# Identify key directories (src\u002F, app\u002F, lib\u002F, etc.)\nmcp__plugin_serena_serena__list_dir({\n  \"relative_path\": \"src\",\n  \"recursive\": true\n})\n```\n\n**Goal**: Identify entry points, main modules, and organizational patterns.\n\n### Phase 2: Entry Point Analysis\n\nFind the application entry points:\n\n```python\n# Look for main\u002Fapp files\nmcp__plugin_serena_serena__search_for_pattern({\n  \"substring_pattern\": \"if __name__.*==.*__main__|def main\\\\(|app\\\\s*=\\\\s*FastAPI|createApp\",\n  \"restrict_search_to_code_files\": true\n})\n\n# Get symbols from entry file\nmcp__plugin_serena_serena__get_symbols_overview({\n  \"relative_path\": \"src\u002Fmain.py\",\n  \"depth\": 1\n})\n```\n\n### Phase 3: Core Component Mapping\n\nIdentify and analyze major components:\n\n```python\n# Find all service\u002Fcontroller\u002Fmodel classes\nmcp__plugin_serena_serena__find_symbol({\n  \"name_path_pattern\": \"Service\",\n  \"substring_matching\": true,\n  \"include_kinds\": [5],  # Class only\n  \"depth\": 1\n})\n\n# For each major component, get full structure\nmcp__plugin_serena_serena__find_symbol({\n  \"name_path_pattern\": \"AuthService\",\n  \"include_body\": false,\n  \"depth\": 1  # Get methods\n})\n```\n\n### Phase 4: Dependency Tracing\n\nUnderstand how components connect:\n\n```python\n# Find who uses AuthService\nmcp__plugin_serena_serena__find_referencing_symbols({\n  \"name_path\": \"AuthService\",\n  \"relative_path\": \"src\u002Fservices\u002Fauth.py\"\n})\n\n# Find what AuthService depends on\nmcp__plugin_serena_serena__find_symbol({\n  \"name_path_pattern\": \"AuthService\u002F__init__\",\n  \"include_body\": true\n})\n```\n\n### Phase 5: Create Architectural Memories (Optional)\n\nStore findings in Brain memory notes:\n\n```python\n# Write a Brain memory note for architectural insight\nmcp__plugin____brain__write_note({\n  \"title\": \"ANALYSIS-001 AuthService Architecture\",\n  \"content\": \"---\\ntitle: ANALYSIS-001 AuthService Architecture\\ntype: analysis\\ntags: [auth, jwt, architecture]\\n---\\n\\n# ANALYSIS-001 AuthService Architecture\\n\\n## Observations\\n\\n- [fact] AuthService handles JWT validation, user sessions, and OAuth flows #auth\\n- [fact] Dependencies: UserRepository, TokenService, CacheService #dependencies\\n- [fact] Used by all API endpoints via middleware #integration\\n\\n## Relations\\n\\n- part_of [[Project Architecture]]\\n- depends_on [[UserRepository]]\\n- depends_on [[TokenService]]\",\n  \"folder\": \"analysis\"\n})\n```\n\n### Phase 6: Entity Graph Creation (Optional)\n\nCreate Brain memory notes for major components with relations:\n\n```python\n# Create component note with relations\nmcp__plugin____brain__write_note({\n  \"title\": \"ANALYSIS-002 Component Graph\",\n  \"content\": \"---\\ntitle: ANALYSIS-002 Component Graph\\ntype: analysis\\ntags: [components, graph, architecture]\\n---\\n\\n# ANALYSIS-002 Component Graph\\n\\n## Observations\\n\\n- [fact] AuthService is central auth component #service\\n- [fact] UserRepository handles data access #repository\\n- [decision] Components linked via dependency injection #pattern\\n\\n## Relations\\n\\n- relates_to [[ANALYSIS-001 AuthService Architecture]]\\n- part_of [[Project Architecture]]\",\n  \"folder\": \"analysis\"\n})\n```\n\n## Relationship Types\n\nStandard relationship types for architecture:\n\n| Type | Use For |\n|------|---------|\n| `uses` | General usage (A uses B) |\n| `depends_on` | Dependency (A requires B) |\n| `calls` | Direct function\u002Fmethod calls |\n| `extends` | Class inheritance |\n| `implements` | Interface implementation |\n| `connects_to` | External connections (DB, API) |\n| `contains` | Composition (A contains B) |\n\n## Entity Types for Architecture\n\n| Type | Use For |\n|------|---------|\n| `Service` | Business logic services |\n| `Repository` | Data access layer |\n| `Controller` | Request handlers |\n| `Middleware` | Request\u002Fresponse processing |\n| `Model` | Data models\u002Fentities |\n| `Library` | External dependencies |\n| `Framework` | Framework components |\n\n## Example: FastAPI Project Analysis\n\n```python\n# 1. Find routers\nmcp__plugin_serena_serena__search_for_pattern({\n  \"substring_pattern\": \"APIRouter\\\\(\\\\)|router\\\\s*=\",\n  \"restrict_search_to_code_files\": true\n})\n\n# 2. Analyze router structure\nmcp__plugin_serena_serena__get_symbols_overview({\n  \"relative_path\": \"src\u002Frouters\u002Fusers.py\",\n  \"depth\": 1\n})\n\n# 3. Find dependency injection\nmcp__plugin_serena_serena__search_for_pattern({\n  \"substring_pattern\": \"Depends\\\\(\",\n  \"restrict_search_to_code_files\": true,\n  \"context_lines_before\": 1,\n  \"context_lines_after\": 1\n})\n\n# 4. Trace service dependencies\nmcp__plugin_serena_serena__find_referencing_symbols({\n  \"name_path\": \"get_current_user\",\n  \"relative_path\": \"src\u002Fdependencies\u002Fauth.py\"\n})\n\n# 5. Create architecture Brain memory note\nmcp__plugin____brain__write_note({\n  \"title\": \"ANALYSIS-003 FastAPI App Structure\",\n  \"content\": \"---\\ntitle: ANALYSIS-003 FastAPI App Structure\\ntype: analysis\\ntags: [fastapi, router, dependency-injection]\\n---\\n\\n# ANALYSIS-003 FastAPI App Structure\\n\\n## Observations\\n\\n- [fact] App uses router-based organization with dependency injection #architecture\\n- [fact] Routers: \u002Fusers, \u002Fauth, \u002Fproducts #routing\\n- [fact] Dependencies: get_current_user, get_db #dependencies\\n- [fact] All routes require auth except \u002Fauth\u002Flogin #security\\n\\n## Relations\\n\\n- part_of [[Project Architecture]]\",\n  \"folder\": \"analysis\"\n})\n```\n\n## Analysis Checklist\n\n- [ ] Directory structure mapped\n- [ ] Entry points identified\n- [ ] Major components catalogued\n- [ ] Dependencies traced\n- [ ] External connections documented\n- [ ] Key patterns identified\n- [ ] Brain memory notes created for insights\n- [ ] Component notes created (if applicable)\n- [ ] Relationships mapped (if applicable)\n\n## Anti-Patterns\n\n| Avoid | Why | Instead |\n|-------|-----|---------|\n| Analyzing every class as a component | Creates noise in knowledge graph | Focus on major architectural components only |\n| Reading full source before overview | Wastes tokens on unneeded code | Start with get_symbols_overview, read selectively |\n| Creating notes without relations | Notes lack context without linked knowledge | Create notes with observations and relations |\n| Skipping dependency tracing | Misses critical coupling relationships | Always run Phase 4 for components you create notes for |\n| Documenting WHAT without WHY | Notes become stale quickly | Focus notes on rationale and trade-offs |\n\n---\n\n## Verification\n\nAfter architectural analysis:\n\n- [ ] Directory structure mapped (Phase 1)\n- [ ] Entry points identified (Phase 2)\n- [ ] Major components catalogued (Phase 3)\n- [ ] Dependencies traced for key components (Phase 4)\n- [ ] Brain memory notes created for insights\n- [ ] Notes linked via relations\n\n---\n\n## Tips\n\n1. **Work incrementally** - Don't try to analyze everything at once\n2. **Focus on interfaces** - Public methods\u002FAPIs matter more than internals\n3. **Document decisions** - Create notes for WHY, not just WHAT\n4. **Use notes sparingly** - Only major components, not every class\n5. **Link across projects** - Architecture patterns often apply elsewhere\n",{"name":5,"model":46,"agents":47,"license":15,"metadata":49,"description":7},"claude-opus-4-5",[48,38],"analyst",{"version":50},"1.0.0","main","2bd10cb7ca989f88dbf338b57957763718eda59b","templates\u002Fskills\u002Fcode-architecture","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain","https:\u002F\u002Fgithub.com\u002Floriensleafs","2026-03-11 23:51:59",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add loriensleafs\u002Fbrain --skill code-architecture",{"tool":63,"command":64},"bunx","bunx skills add loriensleafs\u002Fbrain --skill code-architecture",{"tool":66,"command":67},"pnpm","pnpm dlx skills add loriensleafs\u002Fbrain --skill code-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fcode-architecture\u002FSKILL.md",true,[],[72,86,101,122,139,163],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":41},"01M6CD3KHDHPR633RVP95G4XWN","validation-authority","Treat upstream validators as authoritative. Align local config to them. Use when validation fails unexpectedly, before modifying validator behavior, or when tempted to change upstream tool code.","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fvalidation-authority\u002FSKILL.md",[],[79,80,81,40,82,83,84,38,30,85],"validation authority","validation","config","implementer","behavior","tool","change",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":41},"01M6CD3H29Q8FWN9YETT8YVQTS","using-brain-memory","Guidance for using Brain semantic memory effectively. Applies Zettelkasten atomic note principles with observations and relations. Use when deciding whether to query or create notes, structuring note content, or understanding the semantic knowledge graph.","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fusing-forgetful-memory\u002FSKILL.md",[],[93,32,94,95,96,97,98,40,99,39,100],"using brain memory","content","create","notes","graph","guidance","context","knowledge graph",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":41},"01M6CD3E2KTTMNSWXRJAAZA7D1","threat-modeling","Structured security analysis using OWASP Four-Question Framework and STRIDE methodology. Generates threat matrices with risk ratings, mitigations, and prioritization. Use for attack surface analysis, security architecture review, or when asking what can go wrong.","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fthreat-modeling\u002FSKILL.md",[],[108,109,110,40,111,38,112,113,37,114,115,116,117,118,29,119,120,121],"threat","threat modeling","prioritization","question","architecture review","stride","risk","owasp","methodology","framework","security analysis","security","go","review",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":129,"publishedAt":41},"01M6CD3BC6G0Q2MDNW6X51XHBQ","taste-lints","Custom lints with agent-readable remediation instructions. Enforces taste invariants (file size, naming conventions, structured logging, complexity) and surfaces errors that agents can act on directly. Use when writing or reviewing code to catch style violations early.","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftaste-lints\u002FSKILL.md",[128],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[130,82,131,132,40,133,134,135,136,137,30,138],"taste lints","surfaces","complexity","instructions","remediation","file","logging","qa","writing",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":41},"01M6CD37Z7VD22BH42TG0GM66V","style-enforcement","Validate code against style rules from .editorconfig, StyleCop.json, and Directory.Build.props. Detects line ending violations, naming convention issues, indentation problems, and charset mismatches across C#, Python, TypeScript, and JavaScript. Produces JSON reports for pre-commit hooks and CI pipelines.","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fstyle-enforcement\u002FSKILL.md",[],[146,147,148,149,150,151,82,152,153,154,155,156,137,157,30,158,159,160,161,162],"style enforcement","enforcement","ci","pipelines","directory","hooks","Rules","json","pre-commit","editorconfig","reports","issues","validate","commit","javascript","python","typescript",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":41},"01M6CD35JW73TPMCZBF9DTDEE8","steering-matcher","Match file paths against steering file glob patterns to determine applicable steering guidance. Use when orchestrator needs to inject context-aware guidance based on files being modified.","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fsteering-matcher\u002FSKILL.md",[],[170,40,171,172,99,173,98,135],"steering matcher","files","haiku","orchestrator"]