run-tests
Run the test suite and identify new tests needed for recent code changes. Use when verifying changes work correctly or when asked to run tests.
发现 部署与运维 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Run the test suite and identify new tests needed for recent code changes. Use when verifying changes work correctly or when asked to run tests.
Generate case studies, blog posts, experience updates, and variant content from the knowledge base. Use when user wants to create new CV content, write articles, or generate job-specific variants.
Generate job-targeted CV variants with built-in quality gates. Queries knowledge base, customizes content, runs eval/redteam pipeline.
Multi-perspective project onboarding and sprint briefing. Simulates a cross-functional leadership team (PM, Designer, Architect, Engineer) ramping up on project status. Updates the Current Status section in PRO...
Create, edit, and sync CV content using the knowledge base as source of truth. Unified skill for case studies, blog posts, experience updates, and variant content. Replaces cv-content-generator and cv-content-e...
Captures Dmitrii's distinctive writing voice and preferences for all written outputs. Use when creating case studies, blog posts, articles, documents, emails, proposals, PRDs, specifications, messages, or any w...
List all open intents with progress tracking. Use when the user wants to see what intents are in progress, check completion status, or get an overview of their work.
Generate a Marp presentation from an intent's spec. Use when the user wants to create slides for an intent or asks to make a presentation.
Mark an intent as complete and move to done folder. Use when the user has finished working on an intent and wants to document completion, add PR links, and archive it.
Start a new intent with spec-driven development. Use when the user wants to begin working on a new feature, bug fix, or task and needs to document the problem, solution, and requirements.
When you need to run code before a request completes: auth checks, redirects, headers, A/B testing. **Version Context**: Next.js 16.0+ uses `proxy.ts` (replaces `middleware.ts` from v15 and earlier).
Apply when designing RESTful APIs, defining endpoints, HTTP methods, status codes, and response formats.
Apply when styling components with Tailwind CSS: responsive design, component patterns, and class organization.
When checking if skill content matches current library/framework version.
When building UI components, forms, or any user-facing interface. Check before every frontend PR.
When designing layouts, navigation, forms, or feedback components. Reference for consistent UI decisions.
Apply when improving code structure without changing behavior: reducing duplication, simplifying complexity, or improving readability.
Apply when writing code documentation: JSDoc comments, README files, API documentation, and inline comments.
Apply when writing Supabase client queries for CRUD operations, filtering, joins, and real-time subscriptions.
When writing, reviewing, or validating user stories. Used by ARCHITECT-AGENT and PRODUCT-OWNER.
When implementing backend APIs, database queries, authentication, or handling user input.
Apply when writing reusable functions, components, or utilities that work with multiple types while maintaining type safety.
Apply when building forms with validation, handling form state, or integrating with validation libraries like Zod.
Apply when deciding state management approach: local state, context, Zustand for client state, or TanStack Query for server state.
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。