메뉴
Issue creation workflow for Sando Design System. Creates well-structured GitHub issues for bug reports and feature requests following project conventions. Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Creates minimal boilerplate structure for new Web Components in Sando Design System following COMPONENT_ARCHITECTURE.md 7-file pattern. Generates only what developer requests - no assumptions, no dead code. Ask first, then scaffold component files, tests, stories based on requirements. <example> User: "Create a new Card component" Assistant: "I'll use the component-creator skill to scaffold the sando-card component with the 7-file pattern." </example> <example> User: "I need a new Accordion component with expand/collapse functionality" Assistant: "I'll use component-creator to scaffold sando-accordion with the specified behavior." </example> <example> User: "Scaffold a new input field component" Assistant: "Using component-creator to generate sando-input with the standard 7-file structure." </example>
Compact guidelines digest for Sando Design System agents. Replaces the full `## 📚 MANDATORY: Read Guidelines Before ANY Work` block that is duplicated across every specialist agent. Provides pre-digested, token- efficient rules organized by agent type. Trigger: inject into sub-agent prompts before task-specific instructions to avoid each agent re-reading full .toon guideline files (saves ~2000-5000 tokens per workflow).
PR creation workflow for Sando Design System. Ensures conventional commits, correct branch naming, CI-passing PRs, and well-structured PR bodies. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
Routing table, classification protocol, and ask protocol for the Sando Orchestrator. Extracted from the orchestrator to reduce its context size. Contains the keyword → agent mapping, multi-agent workflow definitions, skill injection reference, and the SDD architectural gate. Trigger: loaded once per session by the orchestrator before any delegation.
Canonical verification protocol for Sando Design System agents. Provides the exact commands, decision trees, and thresholds each specialist agent must run after completing work. Replaces per-agent `<verification>` blocks that are duplicated with slight variations across agents. Trigger: inject into sub-agent prompts so each agent knows exactly what to run and what "done" means.
Sync delta specs to main specs and archive a completed change. Trigger: When the orchestrator launches you to archive a change after implementation and verification.
| name | issue-creation |
| description | Issue creation workflow for Sando Design System. Creates well-structured GitHub issues for bug reports and feature requests following project conventions. Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature. |
| license | Apache-2.0 |
| metadata | {"author":"gentleman-programming","version":"1.0-sando"} |
Use this skill when:
1. Search existing issues for duplicates
2. Choose the correct template (Bug Report or Feature Request)
3. Fill in ALL required fields
4. Submit the issue
5. Once ready, open a PR referencing the issue
Use when: a component, token, story, or agent is behaving incorrectly.
Required fields:
fix(scope): short description (conventional commit format)gh issue create \
--title "fix(input): focus ring not visible in high-contrast mode" \
--body "## Bug Description
The focus ring on sando-input is invisible when the OS is in high-contrast mode.
## Steps to Reproduce
1. Enable high-contrast mode on macOS/Windows
2. Navigate to any page with a sando-input
3. Tab to the input field
## Expected Behavior
A visible focus ring styled with the flavor's focus.ring token.
## Actual Behavior
No focus ring visible — fails WCAG 2.4.7.
## Affected Area
sando-input component, flavor-high-contrast.json tokens"
Use when: proposing a new component, token, story pattern, or agent improvement.
Required fields:
feat(scope): short description (conventional commit format)gh issue create \
--title "feat(skeleton): add skeleton loading state to sando-card" \
--body "## Problem Description
When card data is loading asynchronously, there is no visual placeholder — the UI jumps from empty to populated.
## Proposed Solution
Add a loading boolean prop to sando-card that renders sando-skeleton-* primitives matching the card layout.
## Affected Area
sando-card component, skeleton-creator skill"
Use these scopes in issue titles to match conventional commit scopes:
| Area | Scope |
|---|---|
| Component (specific) | component name: button, input, checkbox |
| All components | components |
| Token system | tokens |
| Specific flavor | flavor-sando, flavor-nori, etc. |
| Storybook | storybook |
| Documentation (MDX) | docs |
| AI agents | agents |
| Build / CI | build, ci |
# Search existing issues before creating
gh issue list --search "keyword"
gh issue list --label "bug"
# Create issue (interactive)
gh issue create
# Create issue with title and body inline
gh issue create --title "fix(scope): description" --body "..."
# View issue
gh issue view <number>