Vibook (pinqy520) — Prompts
Excerpt 1: Core Conceptual Framework (from ROO-PROMPT-EN.md)
## Key Concepts and Relationships
Please clearly understand the following key concepts and their relationships:
1. **Project Repository** - The entire code repository, including all source code, configuration files, and documentation. This is the top-level concept.
2. **Documentation Library** - Content located in the `docs/` folder within the project repository, which provides **detailed descriptions of the project**. It describes the project's architecture, modules, functions, and usage methods through a structured approach, helping developers and AI understand the project.
3. **Rule Files** - Including files in the `.roo/` directory of the project repository and the `.roomodes` file in the root directory, which are **instruction sets specifically designed to guide AI assistants on how to work**. Rule files are not part of the documentation library, but independent configurations.
4. **AI Coding Assistants** - Tools like Roo Code that understand the project by reading the documentation library and work according to the guidance in rule files. AI assistants are roles that **use** the documentation library and rule files.
> **Important**: The documentation library (docs/) describes the project, while rule files are instructions guiding how AI assistants should work. AI assistants learn how to work through rule files and understand project content through the documentation library.
Prompting technique: Explicit concept hierarchy with bold terminology definitions and a bold warning callout. The distinction between "documentation library" (project knowledge) and "rule files" (AI behavioral instructions) is the core mental model the prompt installs in the AI before any action.
Excerpt 2: Task Overview Section (from ROO-PROMPT-EN.md)
## Task Overview
1. **Deeply analyze current project**: Comprehensively understand the project architecture, implementation mechanisms of core modules, key code logic, and scan project directories, code, and existing documentation
2. **Establish documentation system**: Create a documentation directory structure tailored to project characteristics
3. **Implement metadata system**: Add AI-optimized metadata tags to all Markdown documents related to project modules
4. **Create core documents**: Establish navigation and index documents
5. **Configure rule files**: Create appropriate rule files, including mode collaboration rules and MCP usage scenarios
6. **Set up custom modes**: Create specific functional modes (e.g., test and summary)
7. **Set up MCP services**: Configure necessary MCP services and integrate their usage scenarios into the rules
8. **Integrate existing content**: Incorporate existing content into the new documentation structure
Prompting technique: Numbered imperative task list with bold phase names. Each task is a discrete, verifiable action. The ordering is significant: analyze before structuring, structure before populating, configure after the knowledge base exists.
Excerpt 3: Global Rule File (.roo/rules/rules.md)
Use `perplexity` to inquire about unfamiliar information.
Prompting technique: Minimalist single-sentence rule. The entire behavioral rule file is one line. This relies entirely on the Roo Code global rules loading mechanism — the rule applies to all modes and instructs the AI to use Perplexity MCP (if available) for any information gap.
Excerpt 4: Prompt-Engineer Mode Definition (.roomodes)
{
"customModes": [
{
"slug": "prompt-engineer",
"name": "📄 Prompt Engineer",
"roleDefinition": "You are an expert Prompt Engineer specializing in designing, optimizing and evaluating AI prompts. You possess deep understanding of different AI models' capabilities, limitations and response patterns, and can craft precisely structured instructions that produce consistent, accurate and contextually appropriate outputs. Your expertise extends to prompt chain design, complex reasoning frameworks, and technical documentation of prompt systems.",
"groups": ["read", "edit", "mcp"],
"source": "project"
}
]
}
Prompting technique: Expertise declaration with capability enumeration. The mode is scoped to the project (not global), with full read/edit/MCP access.