539건 · 관련도순
Use when refining a draft user prompt before sending it to a coding agent. Decomposes goal/context/constraints/acceptance/output-format, detects ambiguity and model-coupled framing, then emits a model-agnostic rewrite. Supports --analyze, --score, and --deep. NOT for prompts from scratch (mk:brainstorming), plans/reviews (mk:elicit), implementation plans (mk:plan-creator), or general codebase scouting (mk:scout).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when transforming existing code into agent-consumable surfaces — CLI (npm-publishable), MCP server (stdio/SSE/Streamable HTTP), and a companion skill. Triggers on 'agentize', 'henshin', 'expose as MCP', 'wrap as CLI', 'publish to npm', 'make LLM-accessible', 'turn into agent tool', 'expose feature as tool'. Runs when the user has existing code and wants to ship it to agents. NOT for building new code from scratch (see mk:bootstrap); NOT for reviewing or verifying existing code (see mk:review).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bootstrap the central system spec at `docs/system/` for a repository that has never had one. Scans the governed surface, proposes a concept map clustered by directory, and materializes elements + shards ONLY after a human confirms that map. Use when adopting the baseline on an existing project, or when the corpus needs re-deriving from scratch. Re-runnable. Requires `memory.architecture_map.enabled` and a declared `governed_surface`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up, audit, and debug analytics tracking implementation — GA4, Google Tag Manager, event taxonomy, conversion tracking, and data quality. Use when building a tracking plan from scratch, auditing existing analytics for gaps or errors, debugging missing events, or setting up GTM. Trigger keywords: GA4 setup, Google Tag Manager, GTM, event tracking, analytics implementation, conversion tracking, tracking plan, event taxonomy, custom dimensions, UTM tracking, analytics audit, missing events, tracking broken. NOT for analyzing marketing campaign data — use campaign-analytics for that. NOT for BI dashboards — use product-analytics for in-product event analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Practical UI refactoring and visual design review inspired by Refactoring UI by Steve Schoger and Adam Wathan. Use when an AI coding agent needs to improve an existing interface, audit visual polish, redesign a rough UI, review frontend code for hierarchy/spacing/typography/color/depth/image issues, or turn a plain implementation into a cleaner product-quality screen. Do not use for creating UI from scratch, scaffolding a new app, building a new landing page, or designing a new design system unless the user explicitly asks to review or refactor an existing interface.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when auditing UI code for interface-guideline compliance (accessibility, forms, animation, images, performance, UX copy) and/or validating a deployed page against Lighthouse 95+ targets. Produces evidence-based findings (file:line + Lighthouse JSON) and turns confirmed pendencies into Draft SPECs via write-specs. Do NOT use to design/build UI from scratch (use design) or to fix findings inline — fixes go through the SPEC pipeline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when invoked as $new-project or when creating a brand-new repository or project from scratch — scaffolds mise-pinned tools, a just task surface, the standard repo files, and CI for Python (uv), TypeScript (bun), Rust (cargo), or Go.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes and generates llms.txt files -- the emerging standard for helping AI systems understand website structure and content. Can validate existing llms.txt files or generate new ones from scratch by crawling the site.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Polish an existing report, deck, or HTML page to the ReportRoom design bar — visual hierarchy, typography, charts, dark mode, OG/social link preview. Use when the user says "make it beautiful", "improve the design", "it looks plain", "fix the layout" about something already written or published. Not for creating content from scratch (use report-publisher or deck-publisher).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implementação educacional do GPT em ~300 linhas. Reproduz o GPT-2 (124M) em OpenWebText. Código limpo e hackeável para aprender transformers. Por Andrej Karpathy. Perfeito para entender a arquitetura do GPT do zero. Treine em Shakespeare (CPU) ou OpenWebText (multi-GPU).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to edit, review, or improve existing marketing copy — 'edit this copy,' 'proofread,' 'polish this,' 'tighten this up,' 'too wordy,' 'sharpen the messaging.' Use when copy exists and needs improving, not rewriting from scratch. For writing new copy, see copywriting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Track Two / internal innovation system for running small, fast experiments outside the core business. Runs in three modes — Diagnostic for designing the full Protoloop from scratch (intake channels, loop structure, team, exit paths), Review for running the monthly heartbeat meeting (loop-by-loop decisions, forward-loading, portfolio health), and Alert Triggers for defining tripwires that protect, feed, and maintain momentum in the system. Updates company-context.md after every run. Triggers on questions about innovation pipelines, intrapreneurship, Track Two strategy, experimentation systems, handling ideas that don't fit the core business, or building systematic exploration alongside exploitation. Based on 20 years of practice by Eterdis (eterdis.com).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for prototype, MVP, fullstack feature, from-scratch feature, or multi-domain work that needs a SPEC.md before planning or implementation. Do not use for tiny one-file edits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze and refine existing Claude Code Skills for conciseness and effectiveness. Use when asked to "review", "refine", "improve", "optimize" Skills, or when user mentions "skill quality", "skill refinement", "too verbose", "skill doesn't trigger", "description quality", or wants to make a Skill more concise. Do NOT use for creating new skills from scratch (use skill-creator instead).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Initialize a new Convex project from scratch or add Convex to an existing app. Use when starting a new project with Convex, scaffolding a Convex app, or integrating Convex into an existing frontend.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Company Architect: builds a business from scratch as an OKF (Open Knowledge Format) bundle — a tree of version-controllable .md files with frontmatter type, links forming a graph, and reserved index.md/log.md, readable by humans and agents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Conduct a defensible cybersecurity risk assessment using the NIST SP 800-30 Rev 1 methodology: prepare scope and a risk model, identify threat sources and threat events, identify vulnerabilities and predisposing conditions, determine likelihood and impact, compute risk, and communicate results as a prioritized risk register. Use when an organization needs an actual risk *assessment* (not a maturity score), when a control framework (CSF, ISO 27001, RMF, SOC 2, PCI) requires a documented risk analysis as input, when leadership asks "what are our top risks and how bad are they", when assessing risk for a new system or major change, or when building a risk register from scratch. This is the methodology that feeds framework selection, ATO packages, and treatment decisions. Keywords: risk assessment, NIST 800-30, threat modeling, likelihood and impact, risk register, risk analysis, threat sources, vulnerabilities, risk determination, qualitative risk, risk matrix, residual risk, risk treatment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec). Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skill", "audit the skill".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute the full Sophon pipeline: discover → generate → technical → enrich. Use when the user wants to run all steps in one command or build a complete pSEO surface from scratch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.