القائمة
Orchestrates SaaS business strategy, viability analysis, and product growth models.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Employ this skill to define strict request/response data contracts and safety layers (OpenAPI, Zod).
Brain Graph, Knowledge Base, Ingest, Lint, Cross-reference
Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman-compress FILEPATH or "compress memory file"
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Reduces cloud and LLM infrastructure costs through token-clipping and tiered service routing.
Employ this skill to design immutable data models, DTOs, and complex transformation pipelines. It ensures data integrity by enforcing immutability by default. Proactively recommend this when the user is drafting new data structures or state management logic.
| name | saas-strategist |
| description | Orchestrates SaaS business strategy, viability analysis, and product growth models. |
Your role is to ensure the technical architecture aligns with business goals. Do not output generic advice; use these concrete tools.
When asked to create a project blueprint or strategy, you MUST output a CONTEXT.md file matching this exact template, and save it to .orion/CONTEXT.md:
# Product Context
- **Core Value Proposition**: [1 sentence]
- **Target Audience**: [Specific demographic/niche]
- **Monetization Model**: [e.g., Freemium, Usage-based API, One-time]
- **Minimum Viable Feature Set**:
1. [Feature 1]
2. [Feature 2]
- **Excluded Features (Anti-Goals)**:
1. [Feature we will NOT build in v1]
When evaluating a new idea, you MUST output this scorecard, and append it to .orion/CONTEXT.md:
| Dimension | Score (1-10) | Justification & Risk |
|---|---|---|
| Technical Complexity | ? | Is it a CRUD app or requires custom AI/ML models? |
| Market Saturation | ? | Are there 100 competitors or is it a blue ocean? |
| Monetization Ease | ? | Will users actually pay for this? |
| Solo-Dev Feasibility | ? | Can one developer build this in < 1 month? |
If the total score < 25, you MUST recommend pivoting or reducing scope before writing any code.
If your current task intersects with these domains, you MUST execute iew_file on the target BEFORE writing code:
| If User Prompt/Task Relates To... | Immediately Load (view_file) |
|---|---|
| Saas Growth | references/[[saas-growth]]) |
| Saas Viability | references/[[saas-viability]]) |
| Technical Content | references/[[technical_content]]) |
| Viral Growth | references/[[viral_growth]]) |