Tools / Utilities

Token Generator

UUID v4

Base64 Encode / Decode

Unix Timestamp

JWT Parser

QR Code Generator

Explore & Plan Feature / Bug / Change (No-Edit Phase)

You should now focus on exploring the codebase and designing an implementation approach for the following task:

TASK: [DESCRIBE THE FEATURE, BUG, OR CHANGE HERE]

You should:
1. Thoroughly explore the codebase to understand existing patterns, conventions, and structure relevant to this task
2. Identify similar existing features, modules, or architectural approaches that this work should follow or align with
3. Consider multiple implementation approaches and weigh their trade-offs (complexity, performance, maintainability, consistency with existing code)
4. Ask clarifying questions if any part of the requirements or approach is ambiguous
5. Design a concrete, step-by-step implementation strategy, including which files/modules will be affected
6. When ready, present your plan for approval before proceeding

Remember: DO NOT write or edit any files yet. This is a read-only exploration and planning phase.

Execute Mode — Implementation Phase

You should now implement the plan that was previously approved.

TASK: [DESCRIBE THE FEATURE, BUG, OR CHANGE HERE — or reference the approved plan]

You should:
1. Follow the approved plan step by step, implementing changes in logical, reviewable increments
2. Match existing code style, naming conventions, and architectural patterns already present in the codebase
3. Write or update tests alongside the implementation where applicable
4. Flag any point where reality diverges from the plan (e.g. an assumption turns out to be wrong) and pause to explain before proceeding
5. Avoid scope creep — implement what was planned, not additional "nice to have" changes
6. Summarize what was changed and why once implementation is complete

Remember: You now have permission to write and edit files. Stay within the scope of the approved plan unless a deviation is explicitly discussed first.

Review Mode — Code & Plan Audit

You should now critically evaluate the recent changes or proposed plan.

SCOPE: [DESCRIBE WHAT TO REVIEW — e.g. a diff, a PR, a plan, a specific module]

You should:
1. Check correctness: does the implementation do what it claims to do, and does it handle edge cases?
2. Check consistency: does it follow existing codebase conventions, patterns, and style?
3. Check for risk: security issues, performance regressions, breaking changes, or missing tests
4. Distinguish between must-fix issues, suggestions, and nitpicks — don't treat them all as equally urgent
5. Where something is unclear or you're inferring intent, say so explicitly rather than assuming
6. Summarize findings in a structured list, ordered by severity

Remember: This is an evaluative phase, not a fixing phase. Point out issues clearly, but don't make edits unless asked to.