User Persona: The Developer

Profile: Coding, debugging, reading documentation, refactoring, and code review. Primary Goal: Reduce context switching, eliminate boilerplate coding, and accelerate debugging.

Recommended Setup

Providers

• Primary: Anthropic (Claude Sonnet 4.5) is currently top-tier for coding tasks and complex reasoning.
• Local: Ollama (DeepSeek Coder / Qwen 3) for private, offline coding or sensitive IP.
• Speed: Groq (Llama 4) for quick syntax checks and simple transformations.

Spaces

• Space: Current Project (Ingest architectural specs, API docs, key helper classes).
• Space: Library Docs (Ingest the documentation for that obscure library you are using).
• Space: Coding Standards (Your team's style guide, naming conventions, patterns).

Essential Commands

1. "Gen Docstring"

   • Prompt: "Generate XML documentation comments for this method. Include param and return tags with clear descriptions."
   • Usage: Select a function signature.

2. "Find Bug"

   • Prompt: "Analyze this code for potential runtime errors, null reference exceptions, race conditions, or logic flaws. Explain each issue found."
   • Usage: Select a suspicious block of code.

3. "Convert Language"

   • Prompt: "Rewrite this Python code in C#. Maintain equivalent functionality and use idiomatic C# patterns."
   • Usage: Select code to translate between languages.

4. "Explain Regex"

   • Prompt: "Explain what this Regular Expression does step-by-step. Break down each component and provide example matches."
   • Usage: Select a complex regex pattern.

5. "Refactor Clean"

   • Prompt: "Refactor this code to improve readability and maintainability. Apply SOLID principles, extract methods where appropriate, and add inline comments."
   • Usage: Select legacy code or complex methods.

6. "Write Unit Test"

   • Prompt: "Generate unit tests for this method. Include edge cases, null inputs, and boundary conditions. Use xUnit/NUnit syntax."
   • Usage: Select a method to test.

Workflow Example: Debugging

1. Capture: You hit an exception. Screenshot the stack trace.
2. Analyze: Run "Explain Error" on the screenshot (Rephlo supports image input).
3. Context: Rephlo suggests it might be a null object at line 42.
4. Verify: You select the relevant code block and run "Check Null Safety".
5. Fix: Rephlo provides the corrected code snippet with null guards.

Workflow Example: Code Review Preparation

1. Select: Highlight the code changes you're about to submit.
2. Review: Run "Find Bug" to catch issues before your teammates do.
3. Document: Run "Gen Docstring" on any undocumented methods.
4. Polish: Run "Refactor Clean" on complex sections.
5. Submit: Create your PR with confidence.

Supported Code File Types

Rephlo can process and understand the following file types when added to Spaces:

Category	Extensions
C# / .NET	.cs, .csproj, .sln, .xaml
JavaScript / TypeScript	.js, .ts, .jsx, .tsx, .mjs
Python	.py, .pyi, .pyw
Web	.html, .css, .scss, .less
Data / Config	.json, .xml, .yaml, .yml, .toml
Documentation	.md, .txt, .rst
Other Languages	.java, .go, .rs, .rb, .php, .swift

Note: Binary files, compiled outputs, and node_modules are not supported. Keep Space content focused on source files.

Pro Tips for Developers

Keep Space Content Focused

Resist the urge to dump your entire repository into a Space. Instead:

• Include only architectural decision records (ADRs)
• Add key interface definitions and base classes
• Upload API documentation for libraries you're integrating
• Exclude test data, build artifacts, and generated files

A focused Space produces more relevant and accurate responses.

Be Aware of Token Budgets

Large codebases can exceed token limits quickly. Strategies:

• Create separate Spaces for different modules or services
• Use the most relevant Space for each task, not a "kitchen sink" Space
• For very large files, select only the relevant sections rather than the entire file
• Monitor Space size in the Spaces management panel

Use Commands for Repetitive Refactoring

If you find yourself explaining the same transformation repeatedly:

• Create a dedicated Command with your exact requirements
• Include your team's coding standards in the Command prompt
• Save time on boilerplate like docstrings, null checks, logging patterns

Leverage Chat for Iterative Debugging

For complex debugging sessions where you need to explore multiple hypotheses, use the Chat feature instead of one-shot Commands:

• Share code snippets and get follow-up analysis
• Ask clarifying questions about suggested fixes
• Iterate on solutions with context preserved
• Explore alternative approaches in a dialogue

Access Chat from the left navigation panel.

Suggested Command Groups

Organize your development Commands into functional groups:

Group Name	Commands
Code Review	Find Bug, Check Null Safety, Security Audit
Documentation	Gen Docstring, Explain Code, README Generator
Refactoring	Refactor Clean, Extract Method, Rename Variables
Testing	Write Unit Test, Generate Mocks, Test Coverage
Conversion	Convert Language, Modernize Syntax, Format Code

Create Command Groups in the Commands section to keep your toolkit organized.

Common Patterns Rephlo Helps With

Task	Command to Use
Legacy code understanding	"Explain Code" with project Space
API integration	"Convert Language" + Library Docs Space
Pre-commit checks	"Find Bug" on staged changes
Documentation debt	"Gen Docstring" in batch
Code review prep	"Refactor Clean" before PR

---

Next Persona: For Content Creators or return to For Students.