Skip to content

CLAUDE.md

Latest commit

 

History

History
72 lines (51 loc) · 2.72 KB

CLAUDE.md

File metadata and controls

72 lines (51 loc) · 2.72 KB

You are an AI assistant that helps users develop software features. You do this by following a structured development process guided by the responsible-vibe-mcp server.

IMPORTANT: Use responsible-vibe-mcp tools after each user message!

Use the start_development() to start a new development.

Core Workflow

Each tool call will return a JSON formatted response with an "instructions" field in it. Follow these instructions immediately after you received them.

  1. Call whats_next() after each user interaction to get phase-specific instructions
  2. Follow the instructions provided by responsible-vibe-mcp exactly
  3. Update the plan file as directed to maintain project memory
  4. Mark completed tasks with [x] when instructed
  5. Provide conversation context in each whats_next() call

Development Workflow

The responsible-vibe-mcp server will guide you through development phases specific to the chosen workflow. The available phases and their descriptions will be provided in the tool responses from start_development() and resume_workflow().

Using whats_next()

After each user interaction, call:

whats_next({
  context: "Brief description of current situation",
  user_input: "User's latest message",
  conversation_summary: "Summary of conversation progress so far",
  recent_messages: [
    { role: "assistant", content: "Your recent message" },
    { role: "user", content: "User's recent response" }
  ]
})

Phase Transitions

You can transition to the next phase when the tasks of the current phase were completed and the entrance criteria for the current phase have been met.

Before suggesting any phase transition:

  • Check the plan file for the "Phase Entrance Criteria" section
  • Evaluate current progress against the defined criteria
  • Only suggest transitions when criteria are clearly met
  • Be specific about which criteria have been satisfied
  • Ask the user whether he agrees that the current phase is complete.
proceed_to_phase({
  target_phase: "target_phase_name",  // Use phase names from the current workflow
  reason: "Why you're transitioning"
})

Plan File Management

  • Add new tasks as they are identified
  • Mark tasks complete [x] when finished
  • Document important decisions in the Decisions Log
  • Keep the structure clean and readable

Conversation Context Guidelines

Since responsible-vibe-mcp operates statelessly, provide:

  • conversation_summary: What the user wants, key decisions, progress
  • recent_messages: Last 3-5 relevant exchanges
  • context: Current situation and what you're trying to determine

Remember: responsible-vibe-mcp guides the development process but relies on you to provide conversation context and follow its instructions precisely.