pratik/persona-finance-tracker-demo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
persona-finance-tracker-demo/instructions.md
Pratik Narola ee2f58e4a4 Added markdowns
2025-09-13 17:44:57 +05:30

2 KiB
Raw Permalink Blame History

Task Instructions and Guidelines

This file contains important instructions and suggestions provided during the development process. These instructions must be followed at all times.

Instructions

  1. Package Management: We will be using uv for package management. No need to specify versions - let uv handle the latest available versions.

  2. MCP Servers Usage: We must use the following MCP servers throughout the development process:

    • Context7: To fetch and verify latest docs and examples (as of Sept 2025)
    • Zen MCP server: To chat, analyze and think properly about complex problems
    • Archon MCP server: To track the progress of the task and manage project workflow

  3. Task-Driven Development: Always complete the full Archon task cycle before any coding:

    • Check Current Task → Review task details and requirements
    • Research for Task → Search relevant documentation and examples using Context7
    • Implement the Task → Write code based on research
    • Code Review with Zen: Before marking task as "review" or "done", MUST use Zen MCP server to analyze and review the implementation for quality and functionality. while security is important, it will be reviewed and verified separately.
    • Update Task Status → Move task from "todo" → "doing" → "review"
    • Get Next Task → Check for next priority task
    • Repeat Cycle

  4. Error Resolution: When encountering any errors, bugs, or implementation issues:

    • First: Use Context7 or Perplexity MCP servers to research the latest documentation and solutions
    • Second: Analyze the problem using Zen MCP server for complex debugging
    • Last: Only remove or comment out code as a temporary measure if research confirms it's a compatibility issue
    • Never: Remove functionality without first attempting to research and fix the problem properly

Important: Always review and follow these instructions before making any changes to the codebase.