feat: add D.intelligence Agent Corps (9 skills + shared infra)
Add 9 agent skills (#70-#77, #88) for D.intelligence business operations: brand guardian, brand editor, doc secretary, quotation manager, service architect, marketing manager, back office manager, account manager, and skill update meta-agent. Includes shared Python package (dintel), reference docs, document/quotation templates, service module CSVs, cross-device installer, and comprehensive user guide. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
100
custom-skills/71-dintel-brand-editor/code/CLAUDE.md
Normal file
100
custom-skills/71-dintel-brand-editor/code/CLAUDE.md
Normal file
@@ -0,0 +1,100 @@
|
||||
# D.intelligence Brand Editor & Copywriter
|
||||
|
||||
> **Agent #71** | `dintel-brand-editor` v1.1.0 | D.intelligence Agent Corps
|
||||
|
||||
Generate brand-compliant content and evaluate existing content against the D.intelligence writing style guide.
|
||||
|
||||
## Agent Corps Context
|
||||
|
||||
- **Agent #71** — Brand Editor & Copywriter
|
||||
- **Collaborates with**: Agent #70 (Brand Guardian) for compliance review
|
||||
- **Shared constants**: `dintel-shared/src/dintel/brand.py` (colors, terminology, style tokens)
|
||||
|
||||
## Universal Guardrails
|
||||
|
||||
1. **Never send to clients without Andrew's approval** — All client-facing content requires Andrew's review.
|
||||
2. **Never delete — always archive** — Move outdated content to archive; never permanently delete.
|
||||
3. **Never commit pricing without Andrew's sign-off** — Pricing and fee content requires explicit approval.
|
||||
4. **Korean-first, bilingual notation** — Korean primary; jargon uses 한글(English) notation on first use.
|
||||
5. **Never cross-reference client data without consent** — Client data is siloed by account.
|
||||
|
||||
## Quick Reference
|
||||
|
||||
- **Brand**: D.intelligence — Marketing Intelligence 파트너
|
||||
- **Website**: dintelligence.co.kr
|
||||
- **Slogan**: Think Forward
|
||||
- **Concept**: SMART Marketing Clinic
|
||||
- **Brand Guide**: `../../dintel-shared/references/dintelligence_brand_guide.md`
|
||||
- **Shared Constants**: `../../dintel-shared/src/dintel/brand.py`
|
||||
|
||||
## Source Files — Company Credential
|
||||
|
||||
The current company credential deck lives in the Service Package repository:
|
||||
|
||||
| File | Path |
|
||||
|------|------|
|
||||
| Company Credential 2025 (PPTX) | `Source Files/회사소개/D.intelligence - Company Credential 2025.pptx` |
|
||||
| Company Credential 2025 (PDF) | `Source Files/회사소개/D.intelligence-Company-Credential-2025.pdf` |
|
||||
| Andrew Yim Profile (TXT) | `Source Files/문서 양식/D.intelligence_Profile_Andrew_Yim_2026.txt` |
|
||||
|
||||
When generating or updating credential content, reference these as the current baseline.
|
||||
|
||||
## Usage
|
||||
|
||||
### Generate Content
|
||||
|
||||
```bash
|
||||
# Identify content type, then write following the brand guide
|
||||
# Content types: service-page | magazine-article | training-page | inquiry-page | web-copy
|
||||
```
|
||||
|
||||
1. Determine content type → select matching tone (see Tone Map below)
|
||||
2. Read the brand guide reference for full rules
|
||||
3. Draft content following vocabulary, structure, and punctuation rules
|
||||
4. Run the 14-point checklist before delivering
|
||||
|
||||
### Evaluate Content
|
||||
|
||||
Audit any text against the D.intelligence brand guide:
|
||||
|
||||
1. Read the brand guide reference
|
||||
2. Score each of 14 checklist items as PASS/FAIL/N/A
|
||||
3. Output compliance report with percentage score and priority fixes
|
||||
|
||||
## Tone Map
|
||||
|
||||
| Content Type | Ending Style | Example |
|
||||
|-------------|-------------|---------|
|
||||
| Service/About | ~합니다 존칭 서술체 | "성장 파트너입니다" |
|
||||
| Magazine D. | ~다 간결 서술체 | "역할을 한다" |
|
||||
| Training | ~합니다/~세요 혼용 | "참여하실 수 있습니다" |
|
||||
| Inquiry | ~주시면/~드리겠습니다 | "검토의견을 드리겠습니다" |
|
||||
|
||||
## Non-Negotiable Rules
|
||||
|
||||
- Sino-Korean vocabulary: 극대화, 세분화, 도출, 수립, 진단 (not 늘리기, 나누기, etc.)
|
||||
- Bilingual notation on first use: 핵심 성과 지표(KPI)
|
||||
- Product names in original: Google Analytics 4, Meta ADs, Mixpanel
|
||||
- English titles: Title Case with & (not "and")
|
||||
- Section labels: ALL CAPS
|
||||
- No colloquial: no ~해요, 엄청, 꿀팁, ㅎㅎ, emoji
|
||||
- Sentence length: 40~80 chars, complex structures preferred
|
||||
- Magazine D. articles end with 결론적으로 summary
|
||||
- Article titles: [Category] + question/topic format
|
||||
|
||||
## 14-Point Checklist
|
||||
|
||||
1. English bilingual notation for industry terms
|
||||
2. Logical flow: background → explanation → examples → conclusion
|
||||
3. No colloquial expressions
|
||||
4. Sino-Korean formal vocabulary
|
||||
5. Correct sentence endings per content type
|
||||
6. Proper comma usage for clause separation
|
||||
7. [Category] tag in title (Magazine D. only)
|
||||
8. Brand connective expressions (~을 통해, ~함으로써)
|
||||
9. 결론적으로 conclusion (articles only)
|
||||
10. Data/logic-driven, no emotional language
|
||||
11. English titles in Title Case
|
||||
12. Section labels in ALL CAPS
|
||||
13. CTA language (training=EN, inquiry=KR)
|
||||
14. Bilingual layering (EN title + KR explanation)
|
||||
Reference in New Issue
Block a user