technical-spec
This skill provides technical design rules including environment variable management, architecture design, and build/testing commands. Automatically loaded when discussing architecture, environment variables, build commands, or when "tech stack", "architecture pattern", "environment config", or "build command" are mentioned.
What this skill does
# Technical Design Rules ## Basic Technology Stack Policy TypeScript-based application implementation. Architecture patterns should be selected according to project requirements and scale. ## Environment Variable Management and Security ### Environment Variable Management - Centrally manage environment variables and build mechanisms to ensure type safety - Avoid direct references to `process.env`, obtain through configuration management layer - Properly implement default value settings and mandatory checks ### Security - Do not include `.env` files in Git - Always manage API keys and secrets as environment variables - Prohibit logging of sensitive information - Do not include sensitive information in error messages ## Architecture Design ### Architecture Design Principles Select appropriate architecture for each project and define clearly: - **Separation of Responsibilities**: Clearly define responsibilities for each layer and module, and maintain boundaries ## Unified Data Flow Principles #### Basic Principles 1. **Single Data Source**: Store the same information in only one place 2. **Structured Data Priority**: Use parsed objects rather than JSON strings 3. **Clear Responsibility Separation**: Clearly define responsibilities for each layer #### Data Flow Best Practices - **Validation at Input**: Validate data at input layer and pass internally in type-safe form - **Centralized Transformation**: Consolidate data transformation logic in dedicated utilities - **Structured Logging**: Output structured logs at each stage of data flow ## Build and Testing Use the appropriate run command based on the `packageManager` field in package.json. ### Build Commands - `build` - TypeScript build - `type-check` - Type check (no emit) ### Testing Commands - `test` - Run tests - `test:coverage` - Run tests with coverage - `test:coverage:fresh` - Run tests with coverage (fresh cache) - `test:safe` - Safe test execution (with auto cleanup) - `cleanup:processes` - Cleanup Vitest processes ### Quality Check Requirements Quality checks are mandatory upon implementation completion: **Phase 1-3: Code Quality Checks** - `check` - Biome (lint + format) - `check:unused` - Detect unused exports - `check:deps` - Detect circular dependencies - `build` - TypeScript build **Phase 4: Tests** - `test` - Test execution **Phase 5: Code Quality Re-verification** - `check:code` - Re-verify code quality (clean up side effects from test fixes in Phase 4) ### Auxiliary Commands - `check:all` - Overall integrated check (check:code + test) \*for manual batch verification - `open coverage/index.html` - Check coverage report - `format` - Format fixes - `lint:fix` - Lint fixes ### Troubleshooting - **Port in use error**: Run the `cleanup:processes` script - **Cache issues**: Run the `test:coverage:fresh` script - **Dependency errors**: Clean reinstall dependencies ### Coverage Requirements - **MANDATORY**: Unit test coverage MUST be 70% or higher - **Metrics**: Statements, Branches, Functions, Lines
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.