mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-05-20 22:49:06 +08:00
ec9ace9c54
Translate everything-claude-code repository to Japanese including: - 17 root documentation files - 60 agent documentation files - 80 command documentation files - 99 rule files across 18 language directories (common, angular, arkts, cpp, csharp, dart, fsharp, golang, java, kotlin, perl, php, python, ruby, rust, swift, typescript, web) - 199 skill documentation files Total: 455 files translated to Japanese with: - Consistent terminology glossary applied throughout - YAML field names preserved in English (name, description, etc.) - Code blocks and examples untouched (comments translated) - Markdown structure and relative links preserved - Professional translation maintaining technical accuracy This translation expands ECC accessibility to Japanese-speaking developers and teams. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
97 lines
2.5 KiB
Markdown
97 lines
2.5 KiB
Markdown
---
|
|
name: investor-materials
|
|
description: 投資家向けマテリアル、ピッチデック、財務プレゼンテーション、およびビジネス概要。
|
|
origin: ECC
|
|
---
|
|
|
|
# Investor Materials
|
|
|
|
Build investor-facing materials that are consistent, credible, and easy to defend.
|
|
|
|
## When to Activate
|
|
|
|
- creating or revising a pitch deck
|
|
- writing an investor memo or one-pager
|
|
- building a financial model, milestone plan, or use-of-funds table
|
|
- answering accelerator or incubator application questions
|
|
- aligning multiple fundraising docs around one source of truth
|
|
|
|
## Golden Rule
|
|
|
|
All investor materials must agree with each other.
|
|
|
|
Create or confirm a single source of truth before writing:
|
|
- traction metrics
|
|
- pricing and revenue assumptions
|
|
- raise size and instrument
|
|
- use of funds
|
|
- team bios and titles
|
|
- milestones and timelines
|
|
|
|
If conflicting numbers appear, stop and resolve them before drafting.
|
|
|
|
## Core Workflow
|
|
|
|
1. inventory the canonical facts
|
|
2. identify missing assumptions
|
|
3. choose the asset type
|
|
4. draft the asset with explicit logic
|
|
5. cross-check every number against the source of truth
|
|
|
|
## Asset Guidance
|
|
|
|
### Pitch Deck
|
|
Recommended flow:
|
|
1. company + wedge
|
|
2. problem
|
|
3. solution
|
|
4. product / demo
|
|
5. market
|
|
6. business model
|
|
7. traction
|
|
8. team
|
|
9. competition / differentiation
|
|
10. ask
|
|
11. use of funds / milestones
|
|
12. appendix
|
|
|
|
If the user wants a web-native deck, pair this skill with `frontend-slides`.
|
|
|
|
### One-Pager / Memo
|
|
- state what the company does in one clean sentence
|
|
- show why now
|
|
- include traction and proof points early
|
|
- make the ask precise
|
|
- keep claims easy to verify
|
|
|
|
### Financial Model
|
|
Include:
|
|
- explicit assumptions
|
|
- bear / base / bull cases when useful
|
|
- clean layer-by-layer revenue logic
|
|
- milestone-linked spending
|
|
- sensitivity analysis where the decision hinges on assumptions
|
|
|
|
### Accelerator Applications
|
|
- answer the exact question asked
|
|
- prioritize traction, insight, and team advantage
|
|
- avoid puffery
|
|
- keep internal metrics consistent with the deck and model
|
|
|
|
## Red Flags to Avoid
|
|
|
|
- unverifiable claims
|
|
- fuzzy market sizing without assumptions
|
|
- inconsistent team roles or titles
|
|
- revenue math that does not sum cleanly
|
|
- inflated certainty where assumptions are fragile
|
|
|
|
## Quality Gate
|
|
|
|
Before delivering:
|
|
- every number matches the current source of truth
|
|
- use of funds and revenue layers sum correctly
|
|
- assumptions are visible, not buried
|
|
- the story is clear without hype language
|
|
- the final asset is defensible in a partner meeting
|