Skip to content
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions packages/docs/content/docs/prompting-guideline.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,14 @@ This guide offers practical strategies to boost development workflows.
- **Provide Clear Context:** Use `@` to reference files/folders (e.g., `@api.js`) or `README.pochi.md` for project rules and goals (e.g., coding standards, security priorities).
- **Break Down Tasks:** Split complex problems into steps for stability (e.g., review, then optimize).
- **Ensure Consistency:** Rely on structured prompts (XML/JSON) for repeatable, predictable outputs.
- **Iterate Safely:** Tweak prompts step-by-step, using structure to revert changes if needed.
- **Leverage Pochi Features:** Use `~/.pochi/config.jsonc` for models & MCPs, `README.pochi.md` for agents/rules, Pochi Cloud for shared histories, GitHub/Slack for team work.
- **Iterate Safely:** Tweak prompts step-by-step. Using structured formats like XML or JSON for your prompts makes it easier to track and revert changes if needed.
- **Leverage Pochi Features:**
- Use `~/.pochi/config.jsonc` for models & MCPs.
- Use `README.pochi.md` for project-specific rules.
- Use `.pochi/workflows/` for custom workflows.
- Use `.pochi/agents/` for custom agents.
- Use Pochi Cloud for sharing task histories.
- Use the GitHub & Slack integrations for team collaboration.

## How to Prompt Pochi

Expand Down