Proves guardrails, validators, permissions, hooks, and invariants with controlled pass-fail-pass checks. Use when implementing or reviewing enforcement mechanisms.
원문 언어: 영어
이 프롬프트를 복사해 사용 중인 AI 어시스턴트에 입력하세요.
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/AlthafMjeelani/devbox-config.저장소 README를 불러오는 중…
수집된 skill 122개 중 40개를 표시합니다.
Proves guardrails, validators, permissions, hooks, and invariants with controlled pass-fail-pass checks. Use when implementing or reviewing enforcement mechanisms.
원문 언어: 영어
Use when recording real session token metrics, tool call counts, retries, and estimated costs per verified task.
원문 언어: 영어
Use when designing or evolving REST, RPC, and event schemas with stable contracts, validation, versioning, compatibility, and error schemas.
원문 언어: 영어
Use when designing or reviewing HTTP APIs, service interfaces, events, schemas, request/response contracts, and integration boundaries.
원문 언어: 영어
Use when evaluating proposed designs against modularity, coupling, data flow, scalability, operational complexity, and existing idioms.
원문 언어: 영어
Use when creating end-to-end implementation plans, feature plans, or agentic workflow plans before editing code.
원문 언어: 영어
Use for web browsing, QA, and scraping - headless, CLI-driven, no visible window. Fetch page text, screenshot, click, fill forms, assert elements, run accessibility scans.
원문 언어: 영어
Use when structuring instructions and context to maximize provider prompt caching and reusing verified findings across session steps.
원문 언어: 영어
Use when reviewing a plan, proposal, or change with a CEO/founder lens - problem framing, scope, user value, and strategic alternatives. Works at plan stage or on a diff.
원문 언어: 영어
Use when verifying formatting, linting, builds, test pipelines, migrations, deployment risks, feature flags, and rollback procedures.
원문 언어: 영어
Use when reviewing code, diffs, staged changes, or pull requests for correctness, regressions, maintainability, and missing tests.
원문 언어: 영어
Use when exploring unfamiliar repositories via package manifests, entry points, symbol searches, call sites, and test fixtures without reading entire files.
원문 언어: 영어
Use when preparing a loss-aware pre-compaction checkpoint before context resets or summarizing state to restore execution afterwards.
원문 언어: 영어
Use when identifying the minimum relevant project or feature context, discovering entry points, and tracking authoritative working context across tasks.
원문 언어: 영어
Use when orchestrating several agents in parallel - split a request into independent features, dispatch one crewmate per feature with the `crew` CLI, then stop and report status on request (not continuously) so ready branches can be reviewed and shipped.
원문 언어: 영어
Use when providing an adversarial second opinion on a plan, diff, review, or recent analysis.
원문 언어: 영어
Use when reviewing and authoring database schema changes for table locks, backfills, transactions, reversibility, and deployment sequencing.
원문 언어: 영어
Use when reviewing schemas, migrations, queries, indexes, transactions, data retention, and database-related behavior.
원문 언어: 영어
Use when diagnosing bugs, failing tests, build errors, runtime failures, flaky behavior, or performance regressions.
원문 언어: 영어
Use when recording significant architectural decisions, alternatives considered, trade-offs, rationale, and superseding decisions.
원문 언어: 영어
Use when reviewing UI/UX (planned or implemented) - user flow, design-system consistency, accessibility, state coverage, and AI-slop patterns. For building UI, use frontend-design instead.
원문 언어: 영어
Use when writing or updating README files, docs, examples, setup instructions, API notes, or developer-facing explanations.
원문 언어: 영어
Use when updating affected technical documentation, README files, API specs, and runbooks alongside code changes to prevent stale claims.
원문 언어: 영어
Use when estimating effort, timeline, cost, budget, phases, or rough quotation for client work. Defaults to INR unless another currency is specified.
원문 언어: 영어
Use when reviewing an engineering approach (planned or implemented) - architecture, data flow, edge cases, failure modes, tests, and migration/operational risk.
원문 언어: 영어
Use when explaining code, behavior, repository structure, or implementation details with file references.
원문 언어: 영어
Use when implementing focused production changes following existing patterns, clear tests, safe error handling, and self-review diffs.
원문 언어: 영어
Use when searching for public agent skills, evaluating whether a skill is safe to install, or deciding between existing and custom skills.
원문 언어: 영어
Use for generic frontend UI, UX, responsive layout, accessibility, and visual design improvements across web-facing projects.
원문 언어: 영어
Use when the ship gate needs a structured code review - inspect the branch diff and output findings as a single JSON object classified auto_fix vs ask_user. Output only JSON, no prose.
원문 언어: 영어
Use when managing git workflows, reviewing status and diffs, crafting conventional commits, and drafting pull requests safely.
원문 언어: 영어
Use when creating git commits, drafting commit messages, branch names, or concise git summaries from staged or unstaged changes.
원문 언어: 영어
Interviews the user to resolve requirements and decisions before action. Use only when the user explicitly asks to be grilled, interviewed, challenged, or questioned thoroughly.
원문 언어: 영어
Use when the agent might be hallucinating API signatures, library versions, or configuration syntax. Forces verification against actual code.
원문 언어: 영어
Generate tests for a completed phase based on UAT criteria and implementation
원문 언어: 영어
Generate an AI-SPEC.md design contract for phases that involve building AI systems.
원문 언어: 영어
Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit
원문 언어: 영어
Audit milestone completion against original intent before archiving
원문 언어: 영어
Cross-phase audit of all outstanding UAT and verification items
원문 언어: 영어
Run all remaining phases autonomously — discuss→plan→execute per phase
원문 언어: 영어
README 원본 파일: README.md
README 원본 보기