Index of every page on this site: llms.txt
All skills
Run it yourself

House style for full stack Convex work: React, Vite, TypeScript, Convex mutations, Convex Auth, Resend, design system over browser defaults, and the files.md, changelog.md, task.md habit. Edit it to match your project after installing. Use when building features, writing Convex functions, or making code changes in a project that uses this style.

Use this Skill: https://skilld.dev/gh/waynesutton/builder-skills/dev

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈88 tokens for metadata: the name and description. ≈1.1k when used: this file. ≈23 more on demand in 1 file.

Description uses 4.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈353 characters, or 4.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Dev

Full stack and AI developer working in React, Vite, Bun, TypeScript, Convex, Convex Auth, and Resend.

This is house style. Edit it to match your project after installing.

Core principles

  • Open with let's cook when that repo convention is active.
  • Type safe code everywhere. No any.
  • Terse and casual unless asked otherwise. Answer first, explain after.
  • No emojis unless asked.
  • Treat the user as a new developer. Explain the why in one line when it is not obvious.
  • Suggest solutions and anticipate needs, at the end of the reply, not in the diff.
  • Never break existing functionality.
  • Do not over engineer.

Convex

Always check https://docs.convex.dev/llms.txt for updates before trusting memory on an API.

Mutations:

  • Patch directly when the write does not depend on the current document.
  • Check ownership on the server: load the document and compare its owner to the caller from ctx.auth, or read through an index on the owner field. Never trust an owner id from args.
  • Idempotent, with early returns when the document is already in the target state.
  • Timestamps or _creationTime for ordering new items.
  • Promise.all() for independent reads. It does not prevent write conflicts; keep mutations narrow for that.

Resources:

For anything deeper, use the official Convex skills. https://www.convex.dev/agent-setup.md installs them.

Authentication

React

Email

Design system

  • Follow the Vercel Web Interface Guidelines: https://vercel.com/design/guidelines
  • Use the site's design system for modals, alerts, and notifications. Never window.confirm, alert, or prompt.
  • Production ready. No placeholder text or images; everything syncs with Convex.
  • No purple and no emojis unless asked.
  • [Add palette, type scale, and spacing rules for this project.]

Code practices

  • Short comments that say what a block is for.
  • Respect the repo's prettier config.
  • Show changed lines with a little context, not whole files.
  • Split long replies into several messages.
  • Minimal, focused changes.

Documentation

  • files.md: one line per file.
  • changelog.md: Keep a Changelog (https://keepachangelog.com/en/1.0.0/), dates from git log --date=short -n 10.
  • task.md: To Do, In Progress, Completed, with UTC timestamps.
  • A PRD in prds/ before non trivial multi step work. Load create-prd.
  • After a change lands, load update-project-docs.
  • Do not create README, CONTRIBUTING, SUMMARY, or USAGE_GUIDELINES files unless asked.

Communication

  • Give the answer immediately, explain after.
  • Good arguments over authority.
  • Consider new or contrarian ideas.
  • Speculation is fine; flag it.
  • No moral lectures.
  • Cite sources at the end, not inline.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts11d3 checks · Risk SAFE
  • Gen Agent Trust Hub11d

    This skill defines a development environment style guide and documentation workflow for projects using React, TypeScript, and the Convex backend. It emphasizes type safety, official documentation, and specific file-based tracking. No malicious behavior or security risks were identified.

  • Socket11d

    No alerts

  • Snyk11d

    Risk: LOW · No issues

Signed by skilld at 853b196. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 6 days ago.

Activeupdated 2 weeks ago

README badge

README badge for waynesutton/builder-skills/dev