Skip to content

profile-catalog.md

Latest commit

 

History

History
88 lines (57 loc) · 2.11 KB

profile-catalog.md

File metadata and controls

88 lines (57 loc) · 2.11 KB

Profile catalog

This showcase packages OpenCode configuration as a catalog of installable profiles. A profile is a directory that contains operating instructions, agent definitions, skills, themes, and runtime config.

Managed profile contract

Each installable profile must provide:

AGENTS.md
agents/
skills/
opencode.json

A profile may also provide:

themes/
tui.json

The CLI validates this contract before installing a profile.

Profiles

vanilla

Minimal baseline for teams that want OpenCode configured without a heavy workflow model.

Best fit:

  • first-time evaluation;
  • low-friction onboarding;
  • teams that prefer to add their own instructions gradually.

blueprint

Lightweight starter profile with three core agents:

  • plan: read-only planning and analysis;
  • build: implementation and validation;
  • explorer: explicit evidence-gathering pass.

Best fit:

  • teams adopting agentic workflows for the first time;
  • projects that need a shared baseline without strict orchestration;
  • workshops or internal enablement sessions.

streamlined

Direct implementation profile where the primary agents can work in the main thread while specialist agents remain available through explicit user instruction.

Best fit:

  • experienced users who want speed and direct control;
  • day-to-day feature work;
  • small teams that prefer fewer handoffs.

orchestrated

Plan-first workflow with specialized agents for exploration, implementation, testing, debugging, and review.

Best fit:

  • complex changes;
  • review-heavy workflows;
  • teams that want stronger separation between planning and execution.

learning

Educational profile focused on concept breakdown, tutorials, research, and diagrams.

Best fit:

  • onboarding;
  • architecture explanations;
  • learning a new codebase;
  • preparing technical documentation.

How to add a profile

  1. Create a new directory under frameworks/.
  2. Add the required managed entries.
  3. Keep examples generic and public-safe.
  4. Avoid credentials, local paths, logs, and generated files.
  5. Run the CLI tests and sanitization checks before publishing.