메뉴
SkillsMP는 adeonir/agent-skills에서 17개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
수집된 skill 17개 중 17개를 표시합니다.
Creates and evaluates copy for brand, editorial, product, UX, conversion, and informational surfaces. Use when writing, extracting, editing, syncing, critiquing, or auditing copy. Not for visual identity, page layout, or standalone social bios.
원문 언어: 영어
Git workflow for conventional commits, pull request creation, and pull request merging. Use when committing, opening or pushing a pull request, or merging one. Not for code review, acceptance-criteria checks, general branch management, or session wrap-up.
원문 언어: 영어
Spec-driven feature work with traceable requirements, design, tasks, audit, and validation. Use when planning, designing, implementing, or validating a feature. Not for unknown-bug diagnosis, standalone product or technical documents, PR or commit mechanics,…
원문 언어: 영어
Evidence-led debugging for unexpected, silent, or intermittent failures. Use when tracing bugs, adding targeted logs, or verifying fixes. Not for known one-line fixes, runtime review of deployed services, or PM bug triage.
원문 언어: 영어
Clear, precise technical prose that preserves facts, requirements, and terms. Use for explanations, procedures, specifications, documentation, incident reports, and brief factual answers. Not for code-only output, raw logs, compliance certification, or…
원문 언어: 영어
Code review in quick and deep modes, with confidence-scored findings. Use for diff review, guideline audits, re-reviewing fixes, or applying findings before a pull request. Not for acceptance-criteria verification, visual design review, or commit and branch…
원문 언어: 영어
Claude Code rule management at project and user level. Use when defining conventions, scoping, listing, editing, extracting, or deleting rules. Not for procedural workflows, lifecycle hooks, or one-off task instructions.
원문 언어: 영어
Prose editing that removes AI-writing patterns while preserving facts, voice, and format. Use when humanizing or checking a draft for machine-written patterns. Not for authorship detection, source-code changes, fact-checking, translation, or product-copy…
원문 언어: 영어
Conversation handoff scoped to the current project, for resuming work across sessions. Use when checkpointing, ending a session, loading prior context, or clearing a handoff. Not for handoffs between projects, durable session notes, or repository-wide project…
원문 언어: 영어
Obsidian note creation and updates for projects, challenges, achievements, transcriptions, companies, and job applications. Use when documenting work or preserving meeting and lecture notes. Not for session handoffs or repository-wide project context.
원문 언어: 영어
End-of-session context persistence to Obsidian. Use when closing a session, saving work, or documenting what was accomplished. Not for mid-session notes, conversation handoffs, or repository-wide project context.
원문 언어: 영어
Idea exploration from a blank problem space or stress-testing an existing plan before building. Use when comparing approaches, finding gaps, reconsidering a direction, or weighing a pivot. Not for documenting a finalized direction.
원문 언어: 영어
Creates lo-fi wireframes for UI structure and hi-fi mockups for visual directions. Use for landing pages, dashboards, product UI, and app screens. Not for visual identity, copywriting, single-component design, built-UI audits, or code review.
원문 언어: 영어
Visual identity development and validation through the official `DESIGN.md` schema and CLI. Use when creating, refreshing, syncing, previewing, exporting, or diffing design tokens. Not for page layout, rendered variants, product copy, feature specs,…
원문 언어: 영어
Product and technical document creation through guided discovery, including PRDs, positioning docs, Design Docs, and ADRs. Use when defining requirements, strategy, trade-offs, or architecture decisions. Not for UI design, implementation specs, or meeting…
원문 언어: 영어
Roadmap and delivery artifact management in Linear or GitHub. Use when creating, editing, decomposing, moving, or updating roadmaps, epics, stories, bugs, or tasks. Not for implementing a named story, feature status in a spec, project overviews, or quick…
원문 언어: 영어
Analyzes a skill's end-to-end reliability — trigger precision plus compound workflow risk (step count, step nature, variance hotspots) — and proposes verifiable fixes it can apply on confirmation. Use when evaluating a skill's hit rate, checking whether a…
원문 언어: 영어