Loading...
Loading...
Found 14 Skills
This skill should be used when the user asks to "create a business rule", "before insert", "after update", "async business rule", "business rule not working", "current vs previous", or any Business Rule development.
Set up and optimize repositories for AI coding agents. Creates minimal AGENTS.md, CLAUDE.md symlink, docs/REQUIREMENTS.md, docs/BUSINESS-RULES.md, feedback loops, and deterministic enforcement (Claude Code hooks, OpenCode plugins). Use when user wants to make a repo AI-friendly, set up AGENTS.md/CLAUDE.md, document requirements/business rules for AI, add pre-commit hooks for AI workflows, or optimize codebase structure for coding agents.
Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy, clean-architecture, pragmatic-programmer, release-it, system-design, ddia-systems - asking the user questions at every decision point and recording results in the project docs/ folder (TESTING.md, TECH-DEBT.md, RELIABILITY.md, IMPROVE-CODE-QUALITY-PLAN.md) so the journey resumes across sessions. Use when the user wants to harden an AI-generated prototype, add tests before refactoring, make code safe to change, or says 'this works on my machine but I am scared to touch it'. For a large aged codebase, use remove-technical-debt; to decide structure before building, use design-code-architecture; for a product and UX pass, use improve-app. For one framework in isolation, invoke that skill directly.
End-to-end defect hunt and repair across a whole codebase - context and business-rule capture, hierarchical sweeps (business logic, error handling, security, correctness, concurrency, data integrity, performance, config, test quality), reproduction, root-cause fixes, regression proofing, and an evidence-backed audit report. Use whenever bugs are to be found or fixed at repository or module scope, such as "find all the bugs", "fix everything", "audit this codebase", "review the whole codebase", "QA review", "harden this before release", "check for vulnerabilities", "why is this flaky". Use it equally for business-logic defects where nothing crashes but the result is wrong - "the calculation is wrong", "the numbers do not add up", "the discount applies twice", "a step can be skipped", "the request can be replayed", "the limit does not hold", "a user can see another user's data". Prefer this over ad-hoc reading whenever the scope is a repo, a module, or "everything" rather than one known failing line, and when reviewing AI-generated or recently merged code before shipping. This skill CHANGES CODE. If the user wants findings only with nothing modified - "review only", "do not touch anything", "report only" - use anti-bug-review instead.
Read-only defect review of a codebase - deep context and business-rule capture, perspective-based sweeps (business logic, error handling, security, correctness, concurrency, data integrity, performance, config, test quality), reproduction of each finding, severity calibration, and a decision-ready audit report with recommended fixes that are described but never applied. The codebase is left byte-identical. Use this whenever findings are wanted without changes, such as "review this codebase", "audit it but do not touch anything", "code review", "PR review", "second opinion on this code", "security assessment", "due diligence", "is this safe to ship", "what is wrong with this code", "review only", "report only", "read-only review", "check it without changing anything". Use it equally for business-logic defects where nothing crashes but the result is wrong - a wrong total, discount, tax or balance, a skippable step, a replayable action, a quota that does not hold, a user seeing another user's data. Prefer this over anti-bug whenever the user wants a report rather than a repaired repo, when the code belongs to someone else, or when changes need approval first. If the user actually wants the bugs fixed, use anti-bug instead.
Audits this repo for business rules that should live in the central wiki, not here. Activates when the user asks to check for leaks, audit business rules, or validate the wiki/repo boundary.
Registers a boolean condition function and attaches it to triggers via condition_function_id so handlers only fire when the condition passes. Use when gating triggers on business rules, checking user permissions, validating data before processing, filtering high-value orders, rate-limiting events, or conditionally skipping handlers based on payload content.
포킷워크 결재 도메인. 결재선 규칙, 결재 요청, 결재 단계, 알림의 엔티티 정의와 비즈니스 규칙. 결재 관련 기능 구현 시 참고한다.
포킷워크 공지사항/알림 도메인. 공지사항, 카테고리, 개인 알림, 전체 알림의 엔티티 정의와 비즈니스 규칙. 공지/알림 관련 기능 구현 시 참고한다.
포킷워크 연차/휴가 도메인. 연차 유형, 연차 정책(일수 계산), 연차 신청, 휴직 관리의 엔티티 정의와 비즈니스 규칙. 연차/휴가 관련 기능 구현 시 참고한다.
포킷워크 조직관리 도메인. 구성원(직원), 부서, 직책의 엔티티 정의와 비즈니스 규칙. 구성원/부서/직책 관련 기능 구현 시 참고한다.
Configure-Price-Quote (CPQ) vertical skill for the Customware SPA. Defines the section layout, config schema, business rule templates, and deterministic mapping rules for transforming a DOMAIN.md into a CPQ config object. Use this skill when the Builder Agent classifies a customer's domain as a quoting, pricing, or product configuration system. Trigger signals: products with dependencies, price lists, markup/margin calculations, quote generation, proposal workflows, accessory compatibility, product configuration options.