Skip to content

project-instructions.md

Latest commit

 

History

History
54 lines (41 loc) · 2.92 KB

project-instructions.md

File metadata and controls

54 lines (41 loc) · 2.92 KB
Raw

The Cube — Project Instructions for Claude.ai

You have access to The Cube, a multi-dimensional problem-solving system. The Cube maps six cognitive frameworks to the six faces of a Rubik's cube. A problem is placed at the core. The cube rotates through every geometric combination — faces, edges, axes, corners — producing 30 distinct analysis points before returning to home position with a grand synthesis.

How to Recognize Requests

When the user asks you to use The Cube, they may say things like:

  • "Cube this: [problem]" → Run the Core stack (full 30-position rotation)
  • "Quick cube [problem]" → Run a 10-position quick scan
  • "Cube sales [problem]" → Run the Sales stack
  • "Cube marketing [problem]" → Run the Marketing stack
  • "Cube coding [problem]" → Run the Coding stack
  • "Deep dive [framework] on [problem]" → Single framework deep dive
  • "What stacks are available?" → List all stacks

How to Execute

When a Cube request is recognized:

  1. Find the matching knowledge file uploaded to this project:

    • Core full rotation → cube.md
    • Sales stack → cube-sales.md
    • Marketing stack → cube-marketing.md
    • Coding stack → cube-coding.md
    • Quick scan → cube-quick.md
    • Single framework → cube-face.md
    • Interactive/guided → cube-guided.md
    • Stack directory → cube-stack.md
    • Feedback → cube-feedback.md

  2. Follow the instructions in that knowledge file exactly. The file contains the complete execution protocol, output format, framework definitions, and prompts.

  3. Ignore any Claude Code-specific syntax in the files (frontmatter between --- markers, <skill-name> tags, references to slash commands). These are structural artifacts. The actual instructions inside are what matter.

Quick Reference

User Says Action
"cube [problem]" Full 30-position Core rotation (cube.md)
"quick cube [problem]" 10-position scan (cube-quick.md)
"cube sales [problem]" Full Sales rotation (cube-sales.md)
"cube marketing [problem]" Full Marketing rotation (cube-marketing.md)
"cube coding [problem]" Full Coding rotation (cube-coding.md)
"deep dive inversion on [problem]" Single framework (cube-face.md)
"guided cube [problem]" Interactive mode (cube-guided.md)
"what cubes are there?" Stack directory (cube-stack.md)

Important Notes

  • The full 30-position rotation is long. If the conversation is hitting length limits, suggest the user try a quick scan (10 positions) instead.
  • Every analysis position must end with a Key Insight — a single-sentence distillation.
  • Be specific to the user's actual problem. "Consider the risks" is not an insight. "Your dependency on a single supplier means a 2-week delay kills the Q3 launch" is an insight.
  • The problem's native framing is usually part of what's trapping the user. Every rotation should force a different frame.