validation-boundary
Validate at the boundary with Zod schemas and branded types. Business functions trust validated input.
发现 编程开发 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Validate at the boundary with Zod schemas and branded types. Business functions trust validated input.
Ensures questions are answered literally before taking action. Triggers on user input containing '?' or patterns like 'why did you...?', 'will that work?', 'have you considered...?'. Use when user asks about yo...
Visualization is communication. Chart selection, encoding hierarchy, accessibility, rendering performance. Use established algorithms - these problems are solved.
Enforce patterns with TypeScript beyond strict:true. Include noUncheckedIndexedAccess, erasableSyntaxOnly, ts-reset, and type-fest. Advanced type patterns and ESLint enforcement.
Modern React architecture patterns and web interface guidelines. Container/View split, framework adapters, React Query, dependency injection, Storybook-first development, accessibility, interactions, animations...
Use when you have a design or requirements for a multi-step task, before writing code. Creates bite-sized TDD task plans with exact file paths, complete code, and verification steps.
Test pyramid approach with unit, integration, and load tests. DI enables testability. Use vitest-mock-extended for typed mocks.
Use when facing 2+ independent tasks that can be worked on without shared state. Dispatch one agent per problem domain for concurrent investigation.
Treat questions as literal questions. Answer them honestly without interpreting as hidden instructions. STOP after answering - don't immediately act on assumed implications.
Load testing, chaos engineering, and performance validation. Prove your system works under pressure with k6, trace correlation, and progressive load profiles.
Use when about to claim work is complete, fixed, or passing. Requires running verification commands and confirming output before making any success claims. Evidence before assertions, always.
Validate config at startup, secrets in memory only. Never read config during requests, never store secrets in env vars. Use node-env-resolver for multi-source config.
Use when starting feature work that needs isolation from current workspace. Creates isolated git worktrees with directory selection, safety verification, and baseline testing.
Use when working in mm-ibkr-gateway to access market data, account summary, positions, PnL, or orders directly in Python via ibkr_core. Covers connecting with IBKRClient, using market/account/order helpers, and...
Use when working in mm-ibkr-gateway to access market data, account summary, positions, PnL, or orders via the REST API (FastAPI). Covers starting the API server, required env and safety settings, authentication...
STAR framework competency mapping, grounded answer generation, validation, variants, and review workflows for interview questions. Use when asked to produce or validate STAR answers based on a resume.
Gap analysis, company research, narrative generation, template-based cover letter creation, tone customization, and editing workflows. Use when asked to write or personalize cover letters grounded in resume evi...
ATS scoring integration, analysis, optimization suggestions, format compatibility checks, and score tracking. Use when asked to improve ATS scores, interpret Jobscan results, or generate ATS-safe recommendation...
Resume parsing, matching, customization, and export workflows for ATS-friendly resumes. Use when asked to parse resumes, compare to job postings, generate tailored resume variants, or preserve formatting in PDF...
This is a new rule
Review and approve GitLab merge requests using glab CLI
Self-critique loop that catches mistakes before finalizing - "I'm in danger" detection
Enable voice conversations with Claude Code - speak commands and hear responses
This skill should be used when the user asks to "take a note", "add a task", "remind me to", "what's on my agenda", "find my notes about", "capture this", "journal entry", "add todo", "show my tasks", "search m...
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。