Concepts¶
These concepts explain the parts of rp1 that normal users interact with: workflows, projects, context, artifacts, Arcade, reviews, and team handoffs. You do not need to understand rp1 prompt authoring or runtime internals to use the product.
-
Workflows
A workflow is a guided path for a job such as shipping a feature, reviewing a PR, investigating a bug, or generating project context.
-
Project Context
Project context gives rp1 enough knowledge about your codebase to follow its architecture, language, and patterns.
-
Artifacts
Workflows leave durable files behind: requirements, designs, task lists, reports, reviews, walkthroughs, and readiness notes.
-
Arcade
Arcade shows active and completed workflows, attention needed, artifacts, links, and comments in one place.
-
Reviews
PR review workflows produce findings and walkthroughs so you can decide whether to proceed, fix, or ask for a deeper look.
-
Teams
Shared project context and artifacts help teammates understand what was planned, changed, reviewed, and released.
Core User Concepts¶
| Concept | What It Is | Why It Matters |
|---|---|---|
| Workflows | Job-specific commands with built-in guidance | You can run a short command and get a consistent path through planning, implementation, review, or analysis |
| Project context | Generated knowledge about your codebase | rp1 can follow your project structure, terminology, and patterns |
| Artifacts | Files created by workflows | You can inspect, share, resume, and review work after the chat session ends |
| Arcade | Local dashboard for workflow activity | You can see running work, attention needed, artifacts, links, and comments |
| Reviews | PR analysis and walkthrough outputs | You can decide whether to approve, request changes, or investigate |
| Teams | Shared context and handoff material | Teammates can see the same project understanding and delivery artifacts |
Where to Start¶
New to rp1? Start with Getting Started, then read Consistent Workflows to understand why rp1 workflows feel more structured than ad-hoc prompting.
Want output that fits your codebase? Read Project Context to learn how knowledge-build supports later workflows.
Using Arcade? See Arcade, Artifact Viewer, and Annotations.
Reviewing PRs? See the PR Review Guide and PR Review Reference.
Onboarding teammates? See Team Onboarding and project-birds-eye-view.