1.6천건 · 관련도순
Use before implementing any feature, behavior change, or refactor - settles requirements and design, then gets the design independently reviewed and approved by the user before code is written
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
FastAPI best practices and conventions. Use when working with FastAPI APIs and Pydantic models for them. Keeps FastAPI code clean and up to date with the latest features and patterns, updated with new versions. Write new code or refactor and update old code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Best practices for agents managing PostHog skills via the MCP `llma-skill-*` tools — how to discover, read, create, update, and refactor skills efficiently, especially large skills with many bundled files. Use whenever you are about to call any `llma-skill-*` tool, asked to author or edit a shared skill, or troubleshoot why a skill write was rejected. Pairs with `skills-store` (which covers the raw tool surface) by adding the decision-tree, efficiency, and pitfall guidance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test-driven development in Python using uv as the package manager. Covers the red-green-refactor cycle, vertical slicing, and uv project setup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Solve a hard problem by trying multiple approaches in parallel using isolated git worktrees. Each attempt runs in its own branch, and the best solution is selected. Use for complex refactors, tricky bugs, or architectural decisions where multiple strategies could work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Recall project-first and global-supplement ChatCrystal memories before substantive implementation, refactoring, migration, configuration, investigation, or optimization work. Use when the task is non-trivial, has repository or project context, and prior fixes, decisions, pitfalls, or reusable patterns may change the approach.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Code quality patterns and guidelines for ToolUniverse tool development. Apply when writing, fixing, or refactoring tool Python code in the ToolUniverse project. Encodes lessons from 80+ debug rounds. Use alongside devtu-fix-tool and devtu-self-evolve. Triggers: implementing tool fixes, writing new tool classes, reviewing tool code quality, checking schema correctness, looking up API-specific bug fixes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract reusable components, product patterns, and design tokens into a clearer design system with shared APIs, documented defaults, and better reuse. Use when the user wants to refactor repeated UI, consolidate buttons/cards/forms/sections, build a component library, or turn one-off values into reusable tokens.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Restructure existing code while preserving observable behavior. Use for targeted technical debt or hotspot work with characterization tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Discipline skill — TDD red-green-refactor cycle. Use when implementing any feature or bugfix, before writing implementation code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write, review, or audit this repository's technical documentation, including README.md, CONTRIBUTING.md, root and scoped AGENTS.md files, docs pages, and documentation drift. Use for source-backed documentation authoring, behavior verification, and cross-surface consistency. Do not use for code review, deslop diff cleanup, or whole-page rewrites, splits, or reorganizations handled by docs-refactor.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Keep GPT-5.6 and other coding-agent work proportional to the request by locking scope, choosing the smallest sufficient implementation, matching verification to risk, and stopping when success is proven. Use for implementations, bug fixes, refactors, reviews, or maintenance where scope creep, speculative abstractions, unrelated cleanup, repeated test runs, unnecessary dependencies, or polishing beyond the request are risks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Spring Boot 3 patterns for configuration, DI, and web services. Trigger: When building or refactoring Spring Boot 3 applications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides agents through Red-Green-Refactor with runner-captured evidence. Use when running /cc-tdd-cycle, writing tests before implementation, or Global TDD required is yes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Iteratively detects and auto-fixes technical debt in a codebase using three quality criteria from debt-analysis references: conditional branch simplification, encapsulation, and separation of concerns. Applies fixes directly to code, runs existing tests to verify no regressions, re-analyzes, and loops until all high-severity issues are resolved or max iterations (5) reached. Use this skill when you want to automatically improve code quality with real code changes, reduce technical debt systematically, or clean up code to meet quality standards. Trigger on phrases like "fix technical debt", "clean up code quality", "refactor and fix issues", "improve code quality automatically", "apply debt fixes", "fix code problems", "eliminate debt".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library. Use when the user asks to create components, refactor repeated UI patterns, build a design system, or extract tokens.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Combine React's official "You Might Not Need an Effect" guidance with this project's stricter no direct useEffect stance. Use when writing, reviewing, or refactoring React components that might reach for useEffect, derived state, event relays, reset logic, subscriptions, or client fetching.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.