agentleFS
waynesuttonwaynesutton/convexskills/skills/dev/SKILL.md

dev

Skill404 starsChanged 49 days agoApache-2.0View on GitHub

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.

54 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use metrics-graphana, control-flow and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • slopusSkill

    metrics-graphana

    Query and manage Grafana dashboards and Prometheus metrics for Happy infrastructure. Covers grafanactl CLI usage, direct Prometheus queries through Grafana proxy, and dashboard-as-code workflows. Use when user asks about metrics, dashboards, monitoring, Grafana, Prometheus, or wants to add/modify panels.

    Also in 3 projects that use this

  • slopusSkill

    control-flow

    Analyze and design control flows and data structures. Produces compact ASCII tree diagrams showing triggers, call chains, payload shapes, state mutations, and re-render effects. Use when user asks to diagram, trace, visualize, or design a flow or data structure.

    Also in 3 projects that use this

  • MicrosoftSkill

    sessions

    Core principles and workflow router for changes to the Agents Window under src/vs/sessions.

    Also in 3 projects that use this

  • AnthropicSkill

    office-hours

    Set up and run Claude Code office hours, including the calendar event when the champion's own calendar connector allows it. Use when a champion wants a regular time for teammates to bring problems.

    Also in 3 projects that use this

  • nicepkgSkill

    team

    根据任务快速组建临时 AI Agent 团队协作。自动从 .claude/agents/ 中选择最合适的成员组队。

    Also in 3 projects that use this

  • Microsoft AzureSkill

    test

    Also in 5 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. 0 are common, 10 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 35 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No emojis unless asked.

    line 17
  2. Distinctive:

    Treat the user as a new developer.

    line 18
  3. Distinctive:

    Never break existing functionality.

    line 20
  4. Distinctive:

    Do not over engineer.

    line 21
  5. Distinctive:

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

    line 25
  6. Very specific:

    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 …

    line 30
  7. Distinctive:

    Use Convex Auth: https://docs.convex.dev/auth/convex-auth, and Convex Auth v2 at https://auth-v2.previews.convex.dev/.

    line 54
  8. Very specific:

    Read the caller with ctx.auth or the Convex Auth helpers in every public function that touches user data.

    line 56
  9. Very specific:

    Read https://react.dev/learn/you-might-not-need-an-effect before adding a useEffect.

    line 60
  10. Distinctive:

    Follow the React docs: https://react.dev/learn

    line 62
  11. Distinctive:

    Follow the Vercel Web Interface Guidelines: https://vercel.com/design/guidelines

    line 70
  12. Very specific:

    Use the site's design system for modals, alerts, and notifications.

    line 71
  13. Distinctive:

    No purple and no emojis unless asked.

    line 73
  14. Very specific:

    After a change lands, load update-project-docs.

    line 90
  15. Very specific:

    Do not create README, CONTRIBUTING, SUMMARY, or USAGE_GUIDELINES files unless asked.

    line 91
  16. Distinctive:

    Consider new or contrarian ideas.

    line 97

“Common” is measured: kept by at least 6 in 10 of the 35 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.