aqwsde321
- 16 skills
- 0 followers
- 6 hours ago last updated
- ▌ Tdd · aqwsde321 bundleTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
- ▌ Teach · aqwsde321 bundleBuild and continue a stateful, source-grounded teaching workspace with short HTML lessons, practice, reference material, and learning records. Use only when explicitly invoked as $teach for learning a topic across sessions, including a code change supplied as a commit, branch, diff, patch, or current-changes scope; do not use for a one-off explanation.
- ▌ Handoff · aqwsde321 bundleCreate a redacted, portable handoff document that lets a fresh agent or session resume the current conversation without replaying the transcript. Use only when explicitly invoked as $handoff or when an active workflow explicitly requires a cross-session or cross-agent transfer; do not use for an ordinary summary or native Codex task transfer.
- ▌ Wayfinder · aqwsde321 bundlePlan work too large and uncertain for one Codex task as a shared map of decision tickets, then resolve one ticket at a time until the path to the destination is clear. Invoke only through $wayfinder with a loose project idea or an existing map.
- ▌ Code Review · aqwsde321 bundleReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
- ▌ Port Processes · aqwsde321 bundle로컬 TCP 리스닝 포트의 bind 주소, 소유 프로세스, 실행 파일, 작업 디렉터리와 정리 판단을 보여주고, 사용자가 명시적으로 요청한 뒤 해당 사용자 소유 서버 프로세스만 안전하게 종료한다. 로컬 서버·포트 확인, 특정 포트의 PID 확인, 개발 서버 정리 요청에 사용한다.
- ▌ Diagnosing Bugs · aqwsde321 bundleDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
- ▌ Domain Modeling · aqwsde321 bundleBuild and sharpen a project's domain model. Invoke through $domain-modeling when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or another skill explicitly delegates glossary or ADR maintenance. Do not use for source-grounded project-context documentation.
- ▌ Project Context · aqwsde321 bundleRead existing or explicitly create, refresh, remove, and validate source-grounded project routing documentation for a code repository. Use when the user asks for repository project context, "프로젝트 컨텍스트 세팅", "프로젝트 컨텍스트 문서 갱신", "프로젝트 컨텍스트 제거", or invokes "$project-context". Do not trigger for ordinary implementation, debugging, or review merely because onboarding docs are missing.
- ▌ Change Explainer · aqwsde321 bundleTeach a fixed-point code change or supplied patch as a source-grounded walkthrough organized by concepts and execution flow instead of a file-by-file diff summary. Use only when explicitly invoked as `$change-explainer` with a commit, branch, tag, base, patch, diff, or explicit current-changes scope, especially for cross-module behavior, migrations, state or concurrency changes, and unfamiliar frameworks. Do not use for defect review, implementation, or durable project documentation.
- ▌ Codex Gpt Review · aqwsde321 bundleRun an evidence-based review loop between Codex and ChatGPT through the in-app browser. Use when Codex must create a dedicated ChatGPT review conversation or continue an explicitly selected or URL-supplied ChatGPT conversation, summarize its existing context, wait for login, send a diff or artifact for adversarial review, classify findings, apply and verify supported changes, repeat only when new evidence exists, and rename only chats that may be safely changed.
- ▌ Solution Capture · aqwsde321 bundleCapture solved problems, debugging outcomes, project-specific decisions, or reusable workflow patterns as durable Markdown notes under docs/solutions. Use when invoked as `$solution-capture` or through Korean shortcuts such as "해결기록", "해결지식", "지식축적", "컴파운드", "문제 해결 기록", or when the user asks to document lessons learned after fixing, debugging, reviewing, or setting up something.
- ▌ API Design Review · aqwsde321 bundleUse when a user asks to review a feature plan or flow document and draft API endpoints, request/response fields, processing notes, and API design edge cases before implementation, including Korean shortcuts such as "API리뷰", "엔드포인트리뷰", "API 설계 리뷰", "API 초안 작성", or "기획서리뷰" when the flow is already confirmed. Project-specific API conventions and OpenAPI specs override Spring/REST fallback conventions.
- ▌ Exploration Trace · aqwsde321 bundleRecord and visualize the actual project exploration performed while answering a user's question, including searches, files read, line ranges, reasons, findings, and file relationships. Use when the user explicitly invokes $exploration-trace or asks to see the search/read order, exploration log, file-level evidence, or Mermaid graph. This skill observes the task; it does not choose or expand the investigation scope.
- ▌ Feature Flow Review · aqwsde321 bundleUse when a user asks to review, design, or document a new feature flow before API design or implementation, including Korean shortcuts such as "기능플로우리뷰", "플로우리뷰", "기능 흐름 정리", or "플로우 문서 작성". Use especially for multi-step features with user branching, state transitions, permissions, tokens, approval, signup, authentication, payment, settlement, account linking, or external integrations.
- ▌ Skill Quality Review · aqwsde321 bundleAudit the active Codex skill catalog as a suite, then drill into specified or high-risk skills for trigger precision, information structure, guidance, pruning, and behavior-backed validation. Invoke only through $skill-quality-review; with no target audit the current active catalog, with a skill target perform a deep review, and with a directory target audit that suite. Do not scaffold a new skill.