mirror of
https://github.com/alkimake/paperclip.git
synced 2026-06-14 01:50:39 +09:00
## Thinking Path > - Paperclip orchestrates AI agents for zero-human companies > - Hiring new agents depends on clear, reusable operating instructions > - The create-agent skill had one large template reference that mixed multiple roles together > - That made it harder to reuse, review, and adapt role-specific instructions during governed hires > - This pull request splits the reusable agent instruction templates into focused role files and polishes the agent instructions pane layout > - The benefit is faster, clearer agent hiring without bloating the main skill document ## What Changed - Split coder, QA, and UX designer reusable instructions into dedicated reference files. - Kept the index reference concise and pointed it at the role-specific files. - Updated the create-agent skill to describe the separated template structure. - Polished the agent detail instructions/package file tree layout so the longer template references remain readable. ## Verification - `pnpm install --frozen-lockfile --ignore-scripts` - `pnpm --filter @paperclipai/ui typecheck` - UI screenshot rationale: no screenshots attached because the visible change is limited to the Agent detail instructions file-tree layout (`wrapLabels` plus the side-by-side breakpoint). There is no new user flow or state transition to demonstrate; reviewers can verify visually by opening an agent's Instructions tab and resizing across the single-column and side-by-side breakpoints to confirm long file names wrap instead of truncating or overflowing. ## Risks - Low risk: this is documentation and UI layout only. - Main risk is stale links in the skill references; the new files are committed in the referenced paths. > For core feature work, check [`ROADMAP.md`](ROADMAP.md) first and discuss it in `#dev` before opening the PR. Feature PRs that overlap with planned core work may need to be redirected — check the roadmap first. See `CONTRIBUTING.md`. ## Model Used - OpenAI Codex coding agent based on GPT-5, tool-enabled local shell and GitHub workflow, exact runtime context window not exposed in this session. ## Checklist - [x] I have included a thinking path that traces from project context to this change - [x] I have specified the model used (with version and capability details) - [x] I have checked ROADMAP.md and confirmed this PR does not duplicate planned core work - [x] I have run tests locally and they pass - [x] I have added or updated tests where applicable - [x] If this change affects the UI, I have included before/after screenshots, or documented why targeted component/type verification is sufficient here - [x] I have updated relevant documentation to reflect my changes - [x] I have considered and documented any risks above - [x] I will address all Greptile and reviewer comments before requesting merge --------- Co-authored-by: Paperclip <noreply@paperclip.ing>
1.7 KiB
1.7 KiB
Agent Instruction Templates
Use this reference when hiring or creating agents. Start from an existing pattern when the requested role is close, then adapt the text to the company, reporting line, adapter, workspace, permissions, and task type.
These templates are intentionally separate from the main Paperclip heartbeat skill so the core wake procedure stays short.
Index
| Template | Use when hiring | Typical adapter |
|---|---|---|
Coder |
Software engineers who implement code, debug issues, write tests, and coordinate with QA/CTO | codex_local, claude_local, cursor, or another coding adapter |
QA |
QA engineers who reproduce bugs, validate fixes, capture screenshots, and report actionable findings | claude_local or another browser-capable adapter |
UX Designer |
Product designers who produce UX specs, review interface quality, and evolve the design system | codex_local, claude_local, or another adapter with repo/design context |
How To Apply A Template
- Open the matching reference in
references/agents/. - Copy that template into the new agent's instruction bundle, usually
AGENTS.md. For hire requests using local managed-bundle adapters, this usually means setting the adapted template asadapterConfig.promptTemplate; Paperclip materializes it intoAGENTS.md. - Replace placeholders like
{{companyName}},{{managerTitle}},{{issuePrefix}}, and URLs. - Remove tools or workflows the target adapter cannot use.
- Keep the Paperclip heartbeat requirement and task-comment requirement.
- Add role-specific skills or reference files only when they are actually installed or bundled.