Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.pre.dev/llms.txt

Use this file to discover all available pages before exploring further.

Agent Skills are your own instructions that get injected into the agent’s prompt on every build. Think of them as the rules you’d give a senior engineer joining your team — code style, preferred libraries, architectural patterns, things to avoid.

​
Examples

  • “Always use Tailwind. Never write inline styles.”
  • “Use Zod for all schema validation. Never use Joi or Yup.”
  • “Prefer server components in Next.js unless a client hook is explicitly required.”
  • “All database queries go through Prisma. No raw SQL.”
  • “Tests must use Vitest, not Jest.”

​
Creating a skill

  1. Open Integrations → Agent Skills
  2. Click Add Skill
  3. Give it a name and a description of the rule
  4. Toggle it on
From that moment on, every project the Coding Agent works on respects the rule.

​
When to use a skill vs. a project-level instruction

  • Skill = applies to every project you build, forever. “I always use Tailwind.”
  • Project-level instruction = applies to one project only. “This project needs to be WCAG AA compliant.”
Skills are your persistent preferences. Project instructions are per-build context.

​
Toggling and editing

Skills have an on/off toggle on the Integrations page. Turn a skill off for one experimental build, turn it back on afterwards. Edits to a skill take effect on the next task the agent picks up.