software-architecture
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
What this skill does
# Software Architecture Development Skill This skill provides guidance for quality focused software development and architecture. It is based on Clean Architecture and Domain Driven Design principles. ## Code Style Rules ### General Principles - **Early return pattern**: Always use early returns when possible, over nested conditions for better readability - Avoid code duplication through creation of reusable functions and modules - Decompose long (more than 80 lines of code) components and functions into multiple smaller components and functions. If they cannot be used anywhere else, keep it in the same file. But if file longer than 200 lines of code, it should be split into multiple files. - Use arrow functions instead of function declarations when possible ### Best Practices #### Library-First Approach - **ALWAYS search for existing solutions before writing custom code** - Check npm for existing libraries that solve the problem - Evaluate existing services/SaaS solutions - Consider third-party APIs for common functionality - Use libraries instead of writing your own utils or helpers. For example, use `cockatiel` instead of writing your own retry logic. - **When custom code IS justified:** - Specific business logic unique to the domain - Performance-critical paths with special requirements - When external dependencies would be overkill - Security-sensitive code requiring full control - When existing solutions don't meet requirements after thorough evaluation #### Architecture and Design - **Clean Architecture & DDD Principles:** - Follow domain-driven design and ubiquitous language - Separate domain entities from infrastructure concerns - Keep business logic independent of frameworks - Define use cases clearly and keep them isolated - **Naming Conventions:** - **AVOID** generic names: `utils`, `helpers`, `common`, `shared` - **USE** domain-specific names: `OrderCalculator`, `UserAuthenticator`, `InvoiceGenerator` - Follow bounded context naming patterns - Each module should have a single, clear purpose - **Separation of Concerns:** - Do NOT mix business logic with UI components - Keep database queries out of controllers - Maintain clear boundaries between contexts - Ensure proper separation of responsibilities #### Anti-Patterns to Avoid - **NIH (Not Invented Here) Syndrome:** - Don't build custom auth when Auth0/Supabase exists - Don't write custom state management instead of using Redux/Zustand - Don't create custom form validation instead of using established libraries - **Poor Architectural Choices:** - Mixing business logic with UI components - Database queries directly in controllers - Lack of clear separation of concerns - **Generic Naming Anti-Patterns:** - `utils.js` with 50 unrelated functions - `helpers/misc.js` as a dumping ground - `common/shared.js` with unclear purpose - Remember: Every line of custom code is a liability that needs maintenance, testing, and documentation #### Code Quality - Proper error handling with typed catch blocks - Break down complex logic into smaller, reusable functions - Avoid deep nesting (max 3 levels) - Keep functions focused and under 50 lines when possible - Keep files focused and under 200 lines of code when possible ## When to Use This skill is applicable to execute the workflow or actions described in the overview. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.