Results for “architect”

Maps, documents, and onboards into an existing codebase by generating seven structured documents covering stack, structure, architecture, conventions, integrations, testing, and concerns.

Generate, edit, and validate draw.io diagram files (.drawio) with correct mxGraph XML structure for flowcharts, architecture, sequence, ER, and UML diagrams.

Generates task-oriented technical documentation with progressive disclosure for READMEs, API docs, architecture docs, and security reports after reverse engineering, penetration testing, or CTF tasks.

Generate clear documentation for each task including technical descriptions, architecture diagrams, and usage guides. Use when documenting completed features, creating README files, writing API documentation, generating architecture diagrams, or maintaining project documentation. Ensures knowledge is preserved and accessible.

Generates Mermaid architecture diagrams from a codebase, including C4 context and container diagrams, sequence diagrams for key flows, ER diagrams from database schemas, and module dependency graphs.

Manages a long-term Markdown knowledge base for software projects, capturing architecture, decisions, and conventions in `.lore/` with commands to init, sync, query, audit, compress, and mirror to platform files.

Generate Excalidraw diagrams from natural language descriptions, supporting flowcharts, relationship diagrams, mind maps, architecture diagrams, and more. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.

Generates hand-drawn-style Excalidraw architecture diagrams from a codebase, including C4 context and container views, sequence diagrams for key flows, ER diagrams from database schemas, and module dependency graphs.

Write and maintain Architecture Decision Records (ADRs) — when to write one, the standard format, status lifecycle, how to link related decisions, and how to surface ADRs in a codebase. Use when asked to "write an ADR", "document this decision", "architecture decision record", "why did we choose X over Y", or "we need a record of this choice". Do NOT use for: general documentation writing — ADRs are specifically for significant architecture decisions.

An ADR records one decision at the moment it is made, with the information that

Performs deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns, risk, and SOLID alignment. Use when the user wants to assess, evaluate, or review the architecture, design quality, dependency structure, coupling, cohesion, or technical debt of an existing part of the codebase. Not for investigating specific bugs, runtime errors, or failures — use investigate. Not for test planning — use automated-test-planning. Not for file-level code review — use code-review. Not for researching open-ended options, prior art, or how something works — use research. Not for designing a new interface or contract — use design-an-api. Not for writing documentation or architectural decision records.

Generates editable diagram source code (Mermaid, Graphviz DOT, PlantUML, SVG) from natural language, code, schemas, or notes for flowcharts, sequence diagrams, ER diagrams, architecture diagrams, and more. Renders to PNG/SVG/PDF on request via a local Python script.

A technical writer who crafts clear, comprehensive documentation. Specializes in README files, API docs, architecture docs, and user guides.

Document architectural decisions in standardized ADR format. This skill should be used when making significant technical decisions, choosing between approaches, establishing patterns, or when other skills (create-plan, implement-plan, brainstorm) identify decisions that need documentation. Triggers on "document decision", "create ADR", "architectural decision", or automatically when invoked by other skills during planning and implementation.

Documents and explains an existing codebase as it is, without suggesting improvements or architectural changes.

Write or maintain technical documentation — READMEs, runbooks, API references, architecture docs — that a specific reader can act on without asking follow-ups.

Generates a comprehensive developer onboarding guide from a codebase, covering tech stack, setup, architecture, conventions, and troubleshooting.

Conduct technical research on technologies and architecture. Use when the user says they would like to do or produce a technical research report

Read every ADR markdown file in docs/adr before making or reviewing decision-sensitive changes. Use when architecture, conventions, or tradeoffs are involved.

Generates thorough README.md documentation by exploring a codebase, identifying the tech stack, and producing setup, architecture, and deployment guides.

Generates thorough README.md files by deeply exploring a codebase to produce comprehensive project documentation covering local setup, architecture, and deployment.

Creates a print-friendly architecture or pipeline presentation deck with a blueprint-grid mask, rust-red callouts, and serif typography.

Analyze a codebase and generate onboarding documentation for engineers, tech leads, and contractors, with fast fact-gathering and repeatable outputs.

Creates C4 context-level system documentation including system descriptions, personas, user journeys, external dependencies, and Mermaid context diagrams.

Translates English Android architecture documentation into Chinese, supporting segment-by-segment input and dynamic adjustments based on user-provided terminology and corrections.

Creates and updates coding standards, conventions, rules, and guidelines for the current project. Use when creating new standards from scratch, converting existing documents into coding standards, or updating existing standards. Does not create architectural decision records — use architectural-decision-record for ADRs. Does not write feature or system documentation — use project-documentation for that. Does not research open-ended options — use research. Does not produce runbooks for operational scenarios — use runbook for that.

Create high-quality bilingual detailed summaries for StaticFlow articles, focusing on evidence, reader value, and clear structure while allowing flexible writing style.

Generates thorough README.md documentation by exploring a codebase, identifying the tech stack and deployment target, and writing detailed setup, architecture, and deployment sections.

Post-ship documentation sync — updates README, CHANGELOG, AGENTS.md, ARCHITECTURE, and TODOS after a release. Ensures docs never drift from code. Run after /commit or /ship before closing a PR.

Creates persona-targeted, step-by-step CodeTour walkthroughs that link to real files and line numbers for onboarding, architecture, PR review, and more.

Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure.

Guides architecture decisions, flow type selection, bulk safety validation, and fault handling standards for Salesforce Flow design and review.

Provides guides for creating diagrams and visualizations using Mermaid, Excalidraw, PlantUML, TikZ, and other tools, covering flowcharts, architecture diagrams, and scientific illustrations.

Generates Excalidraw diagrams programmatically as hand-drawn-style JSON. Use when creating architecture diagrams, flowcharts, or hand-drawn-style visuals for documentation, or when converting existing diagrams to editable Excalidraw JSON.

Build real-time voice and multimodal AI applications using Pipecat and Daily, covering pipeline architecture, AI service integration, and transport options.

Manage software complexity through deep modules, information hiding, and strategic programming, with a scoring framework for evaluating design quality.