agentleFS
Sign inStart free
JackJanoianJackJanoian/deal-desk/skills/dealdesk-dev/SKILL.md

deal-desk-dev

Skill1 starsChanged 6 months agoMITView on GitHub

Develop and operate the DealDesk application. Use when changing DealDesk routes, schema, seeds, tools, UI pages, Quick Hire behavior, role templates, or PE workflow tests.

The file

Show its rules and text

We split this skill into the rules it gives an agent

22 rules. About 0 are common, 20 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈20

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when working on the DealDesk application itself.

    line 14
  2. Distinctive:

    Keep every DealDesk entity company-scoped.

    line 31
  3. Distinctive:

    Prefer structured fields over prose blobs.

    line 33
  4. Distinctive:

    Add migrations for persisted schema changes.

    line 34
  5. Distinctive:

    Keep role templates idempotent through the seeder.

    line 35
  6. Distinctive:

    Do not resurrect retired memo-only flows.

    line 36
  7. Distinctive:

    Keep Quick Hire simple: name, title, instructions, budget, and attached DealDesk skills.

    line 37
  8. Distinctive:

    Read the relevant schema, route, API client, and UI page before editing.

    line 41
  9. Distinctive:

    Update contracts across DB, server, shared validators/types, and UI together.

    line 42
  10. Distinctive:

    Add or adjust focused tests around the changed behavior.

    line 43
  11. Distinctive:

    Run the smallest meaningful verification first.

    line 44
  12. Distinctive:

    Run typecheck for touched packages before handoff.

    line 45
  13. Distinctive:

    Update route serialization and validation.

    line 53
  14. Very specific:

    Update the UI form/table/card.

    line 54
  15. Distinctive:

    Add DB and route tests.

    line 55
  16. Very specific:

    Add the handler under server/src/deal-desk/tools/.

    line 59
  17. Distinctive:

    Add tests for auth, validation, dedupe, and success.

    line 63
  18. Distinctive:

    Keep prompts concise and role-specific.

    line 68
  19. Distinctive:

    Run server startup/seed tests if touched.

    line 70
  20. Distinctive:

    Keep the UX minimal.

    line 74
  21. Distinctive:

    Verify the payload includes budget, role, adapter config, instructions, and desired skills.

    line 77
  22. Distinctive:

    Use focused checks that match the change:

    line 81

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

DealDesk Dev Skill

Use this skill when working on the DealDesk application itself.

DealDesk is a PE-focused layer in this repository. It includes thesis setup, target tracking, intermediary coverage, contact enrichment, role templates, Quick Hire, and DealDesk-specific agent instructions.

Key Areas

  • DB schema: packages/db/src/schema/deal_desk.ts
  • Server routes: server/src/routes/deal-desk.ts
  • Server tools: server/src/deal-desk/tools/
  • Role templates: server/src/deal-desk/seeds/role-templates.ts
  • Quick Hire UI: ui/src/pages/deal-desk/QuickHire.tsx
  • DealDesk pages: ui/src/pages/deal-desk/
  • DealDesk API client: ui/src/api/dealDesk.ts
  • Tests: server/src/routes/deal-desk.test.ts, packages/db/src/deal-desk.test.ts, and focused UI tests where available

Engineering Rules

  • Keep every DealDesk entity company-scoped.
  • Preserve PE language: thesis, target, intermediary, owner, CEO, contact, outreach draft, pipeline, partner review.
  • Prefer structured fields over prose blobs.
  • Add migrations for persisted schema changes.
  • Keep role templates idempotent through the seeder.
  • Do not resurrect retired memo-only flows.
  • Keep Quick Hire simple: name, title, instructions, budget, and attached DealDesk skills.

Development Workflow

  1. Read the relevant schema, route, API client, and UI page before editing.
  2. Update contracts across DB, server, shared validators/types, and UI together.
  3. Add or adjust focused tests around the changed behavior.
  4. Run the smallest meaningful verification first.
  5. Run typecheck for touched packages before handoff.

Common Tasks

Add A DealDesk Field

  • Update packages/db/src/schema/deal_desk.ts.
  • Generate or add the migration.
  • Update route serialization and validation.
  • Update the UI form/table/card.
  • Add DB and route tests.

Add A DealDesk Tool

  • Add the handler under server/src/deal-desk/tools/.
  • Export/register it in server/src/deal-desk/tools/index.ts.
  • Enforce company scoping and input validation.
  • Return structured output with IDs and warnings.
  • Add tests for auth, validation, dedupe, and success.

Update Role Templates

  • Edit server/src/deal-desk/seeds/role-templates.ts.
  • Keep prompts concise and role-specific.
  • Mention relevant DealDesk skills.
  • Run server startup/seed tests if touched.

Update Quick Hire

  • Keep the UX minimal.
  • Send instructions through instructionsBundle, not legacy prompt fields.
  • Attach the DealDesk skill set through desiredSkills.
  • Verify the payload includes budget, role, adapter config, instructions, and desired skills.

Verification Checklist

Use focused checks that match the change:

pnpm vitest run server/src/routes/deal-desk.test.ts packages/db/src/deal-desk.test.ts
pnpm --filter server typecheck
pnpm --filter ui typecheck

For wider changes, add:

pnpm test
pnpm build

Handoff Standard

Report:

  • What DealDesk workflow changed.
  • Which records/routes/UI surfaces are affected.
  • Tests and typechecks run.
  • Any remaining product or data migration risk.

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.

Check your setup, free