'implement' 검색 결과

Reviews one design document for completeness, internal consistency, implementability, and design standards. Before handing to programmers.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit planned SaaS entities against implemented files on disk — routes, UI components, database models, services, and specs. Compare planned vs built.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate missing design or architecture docs from existing implementation — works backwards from code and prototypes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert knowledge of the saksflyt saga pattern implementation in melosys-api. Use when: (1) Debugging or modifying process flows (Prosessinstans, ProsessType, ProsessSteg), (2) Understanding async step execution and locking mechanisms (låsReferanse), (3) Investigating race conditions, OptimisticLockingException, or entity overwrites, (4) Moving event listeners to saga steps to avoid sync/async conflicts, (5) Adding new process types or steps, (6) Deciding whether to use @DynamicUpdate on entities.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Drive Keel agent test-first or evidence-first execution for a selected OpenSpec task. Use when a task needs software tests, hardware testbench, assertions, lint, new behavior proof, regression coverage, or red/green evidence before implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Align explicit requirements, implicit expectations, non-goals, observable acceptance, evidence, and decision authority before OpenSpec specs and executable tasks finalize. Use when authoring or updating a proposal, design, specs, or tasks, or when a request hides a material product choice. Do not use for routine implementation of an already-authorized task, unrelated conversation, or facts the repository can answer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when designing a Spark feature or writing or materially revising a design proposal that needs repository-first research, user input on unresolved key choices, and an owner-aligned implementation plan before code changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a Spark implementation needs an evidence-based review for correctness, ownership, compatibility, failure handling, maintainability, and unnecessary complexity.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a working Spark implementation should be simplified without changing its observed behavior, ownership, compatibility, or public contract.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a Spark change needs its authoritative owner, affected boundaries, risks, acceptance criteria, and smallest verifiable slice established before implementation or review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Integrate and maintain Robelest Convex Auth in apps by always checking upstream before implementation. Use when adding auth setup, updating auth wiring, migrating between upstream patterns, or troubleshooting @robelest/convex-auth behavior across projects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero clean, spacious, readable, and visible on a small laptop.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Set up and configure WorkOS AuthKit authentication with Convex backend. Use when integrating AuthKit, configuring JWT providers, setting up environment variables, or implementing sign in and sign out flows with React and Vite. Supports Netlify deployment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reflection-first problem solving methodology for Convex development. Use before implementing any solution to ensure proper root cause analysis, 98% code confidence, and minimal change scope.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create Convex queries, mutations, and actions with proper validation, authentication, and error handling. Use when implementing new API endpoints.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Set up Convex authentication with proper user management, identity mapping, and access control patterns. Use when implementing auth flows, setting up OAuth providers, or adding role-based access control.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build reactive, type-safe, production-grade backends. ALWAYS use this skill when the user asks to build, plan, design, or implement backend features, APIs, data models, server logic, database schemas, web apps, full stack apps, or mobile apps. This includes planning and architecture discussions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates Strategy pattern for PHP 8.5. Creates interchangeable algorithm families with context class, strategy interface, and concrete implementations. Includes unit tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide for writing high-quality acceptance criteria and acceptance tests using industry-standard BDD (Behavior-Driven Development) and ATDD (Acceptance Test-Driven Development) practices. Use this skill when creating acceptance criteria for user stories, writing Gherkin scenarios, or implementing acceptance test specifications following Given-When-Then format.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issue

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.