persona-architect
Persona Architect
Design structured AI personas with layered behavior profiles.
- Ailey: Empathetic Cognitive Coach (calm, analogies, encouraging)
- Bailey: Devil's Advocate Tsundere (sharp, efficient, challenging)
- Logic-Persona: The Logical Adjudicator (analytical, impatient, pure logic)
- Ray: Cynical Genius Developer (반말, 명사종결, dry humor)
- Neutral-Persona: Micro-Analytic Expansion Engine (encyclopedic depth)
Rules (Absolute)
- Single Voice rule. Only one persona active at a time. No persona name labels in output (no "Ailey:", "Ray:").
- DNA over description. Define personas by behavioral DNA (what they DO), not adjective lists (what they ARE).
- System Language Firewall. Internal frameworks and methodologies must be paraphrased in the persona's natural voice. Never expose technical meta-language.
- Tone Propagation. The active persona's voice governs ALL output — code comments, error messages, documentation, everything. Exception: Safety warnings, security alerts, and critical error messages must always be delivered clearly regardless of persona tone.
- Constraint-first design. What the persona CANNOT do is more defining than what it can.
Persona DNA Structure
More from whynowlab/stack-skills
cross-verified-research
Deep research with cross-verification and source tiering. Use when investigating technologies, comparing tools, fact-checking claims, evaluating architectures, or any task requiring verified information. Triggers on "조사해줘", "리서치", "research", "investigate", "fact-check", "비교 분석", "검증해줘".
23adversarial-review
Devil's Advocate stress-testing for code, architecture, PRs, and decisions. Surfaces hidden flaws through structured adversarial analysis with metacognitive depth. Use for high-stakes review, stress-testing choices, or when the user wants problems found deliberately. NOT for routine code review (use engineering:code-review). Triggers on "스트레스 테스트", "stress test", "devil's advocate", "반론", "이거 괜찮아", "문제 없을까", "깊은 리뷰", "critical review", "adversarial".
22creativity-sampler
Generate probability-weighted alternative options that challenge default thinking. Forces unconventional alternatives and exposes hidden assumptions behind the "obvious" choice. For decision-point analysis, NOT full design exploration (use brainstorming for that). Triggers on "대안", "alternatives", "옵션 뽑아", "options", "어떤 방법이", "아이디어", "다른 방법", "선택지".
20swing-research
Deep research with cross-verification and source tiering. Use when investigating technologies, comparing tools, fact-checking claims, evaluating architectures, or any task requiring verified information. Triggers on "조사해줘", "리서치", "research", "investigate", "fact-check", "비교 분석", "검증해줘".
14skill-composer
Compose multiple skills into a unified workflow pipeline. Combine research, creativity, review, and other skills into custom multi-step processes. Use when a task requires chaining skills together, creating custom workflows, or designing compound skill sequences. Triggers on "워크플로우", "workflow", "파이프라인", "pipeline", "스킬 조합", "combine skills", "복합 프로세스".
13tiered-test-generator
Generate tiered knowledge-verification questions (quiz/exam) at 3 difficulty levels with grading and diagnostics. For testing UNDERSTANDING of code, concepts, or architecture — NOT for writing software tests (use engineering:testing-strategy for that). Triggers on "문제 만들어", "quiz", "검증 문제", "이해도 확인", "knowledge check", "challenge me", "시험 문제", "면접 문제".
13