소스 정보
- 저장소
- ForceInjection/domain-driven-design-skills
- 최근 소스 활동
- 2026년 5월 8일 03:07
- 감지된 SKILL.md 언어
- 영어
- 스타
- 25
- 포크
- 7
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
메뉴
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/ForceInjection/domain-driven-design-skills --skill brand-evolution명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Conduct deep academic research for philosophy, neuroscience, cognitive science, and theoretical computer science (computability, complexity, AI theory, logic). Use when user asks to: research academic topics, find scholarly papers, conduct literature reviews, analyze citations, synthesize research findings, explore philosophical arguments, investigate consciousness/cognition, study computability/decidability/Turing machines, or analyze academic debates. Triggers on: 'research papers', 'literature review', 'academic sources', 'scholarly articles', 'philosophy of mind', 'computability theory', 'neuroscience studies', 'find papers on', 'what does the research say'.
Create clear action plans with steps, success criteria, and risk awareness. Use before implementing features, making changes, starting projects, or anytime you need a roadmap to success. Triggers on "plan this", "how should we approach", "what's the strategy", "steps to complete", or when facing complex multi-step work.
Add keyboard navigation to a feature using CommandRegistryService. Use when implementing keyboard shortcuts, vim-style navigation, or hotkeys for a page or component.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | brand-evolution |
| description | Update and evolve existing brand identity based on new direction or feedback |
| triggers | ["update brand","change brand","evolve brand","rebrand","refresh brand","modify brand","brand update","new direction","pivot"] |
| tools_required | ["load_brand","write_file","read_file","list_files"] |
Use this skill when the user wants to update, evolve, or pivot an existing brand identity rather than creating something entirely new.
Before evolving a brand:
load_brand(detail_level='full') to get complete current identitylist_files("assets/") to see what's been generatedSmall updates that don't change core identity:
Noticeable changes while maintaining recognition:
Significant direction change:
Complete transformation (consider brand-identity skill instead):
Load the brand and review:
- What's working well? (Keep these)
- What needs improvement?
- What's the user asking to change?
Ask about:
Present changes clearly:
## Proposed Evolution
### What Stays the Same
- [Elements being preserved]
- [Reason: maintains equity/recognition]
### What Changes
- [Element]: [Old] → [New]
- [Rationale for change]
### Impact on Existing Assets
- [What needs to be regenerated]
- [What can remain]
After user approval:
Current: Young professionals in urban areas
Evolution: Expanding to suburban families
Changes needed:
- Audience profile update
- Possibly softer tone
- Family-friendly imagery direction
- Messaging adjustments
Current: Heavy, dark color palette
Evolution: Lighter, more modern feel
Changes needed:
- Primary colors (lighter variants)
- Typography (more contemporary)
- Imagery style update
- Logo may need update
Current: Formal, authoritative
Evolution: More conversational, approachable
Changes needed:
- Voice personality description
- Tone attributes
- Messaging do's and don'ts
- Sample copy
Current: Premium luxury positioning
Evolution: Accessible premium
Changes needed:
- Positioning statement
- Value proposition
- Competitor set
- Possibly pricing language in messaging
Before saving evolved brand:
After evolution is approved:
# Update the identity file
write_file("identity.json", updated_identity_json)
# Consider saving previous version
write_file("identity_backup_[date].json", original_identity_json)
Suggest using brand-identity skill instead if:
Be honest: "The changes you're describing are substantial enough that we might get a better result building fresh rather than constraining ourselves to the existing identity. Would you like to create a new brand identity?"
When evolving: