agentleFS
phazurlabsphazurlabs/sumi/skills/business-design-templates/SKILL.md

business-design-templates

Skill58 starsChanged 23 days agoApache-2.0View on GitHub

Client-facing design deliverables: proposals, SOWs, case studies, pitch decks, pricing calculators, project briefs, and handoff documentation. Use when packaging design work for a client, an executive, or a portfolio — the artifact that leaves the team, not the interface itself.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Scope is a fence, not a wish: Every proposal names what is excluded.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Business Design Templates — The Business Side of Design

Mental model

These are the artifacts that leave the team. They are read by people who did not attend the meeting, will not read the Figma, and are deciding whether to fund, approve, or hire.

  • Lead with the decision you want. A proposal that opens with your process makes the reader hunt for the ask. Put scope, timeline and price in the first screen.
  • Show the problem before the solution. A case study that opens on the final UI reads as a portfolio piece. One that opens on the broken funnel reads as evidence.
  • Quantify or say you cannot. "Improved usability" is noise. "Cut checkout abandonment from 71% to 54% over six weeks" is an argument. If you have no number, say what you observed instead of reaching for an adjective.
  • Scope is a fence, not a wish. Every proposal names what is excluded. The excluded list prevents more disputes than the included one.

Index

ArtifactReference
Redesign, new product, design system, UX audit, retainer proposalsproposal-templates.md
Statement of work, scope fencing, pricing structureproposal-templates.md
Design review deck, stakeholder direction pitchpitch-presentation-templates.md
E-commerce and SaaS case study narrativescase-study-templates.md
Portfolio case study structurecase-study-templates.md
Figma handoff practice, developer checklistclient-handoff-templates.md
Token export, asset exportclient-handoff-templates.md
Design spec format, component docs, interaction specdesign-documentation.md
Invoice structure, line items, payment termsinvoice-and-billing.md

Reference architecture

FileCoversLines
references/client-handoff-templates.mdhandoff and export1054
references/proposal-templates.md5 proposal types1016
references/design-documentation.mdspecs and component docs978
references/case-study-templates.mdnarrative + 2 templates920
references/pitch-presentation-templates.md2 deck templates851
references/invoice-and-billing.mdbilling artifacts53

What every reference file contains

  1. The template as fill-in-the-blank prose, not a description of a template
  2. A worked example with realistic numbers
  3. What the reader is deciding, and what they need to decide it
  4. The section people cut that they should not

Routing

For winning the work — redesign, new-product, design-system, UX-audit and ongoing-retainer proposals: read references/proposal-templates.md.

For presenting — design review decks and stakeholder decks for pitching a direction: read references/pitch-presentation-templates.md.

For telling the story afterwards — the case study narrative structure plus e-commerce and SaaS templates: read references/case-study-templates.md.

For handing off to engineering — Figma handoff practice, the developer checklist, token export and asset export: read references/client-handoff-templates.md.

For documenting the system — design spec format, component documentation and interaction specification: read references/design-documentation.md.

For odds and ends — the patterns that had no home in the files above when this skill was converted to a router: read references/business-supplementary.md.

Cross-References

  • figma-design-tool-workflows — Figma-specific handoff and dev mode workflows
  • ux-metrics-measurement — Metrics frameworks for case study results sections
  • design-systems-architecture — Design system documentation patterns
  • ux-research-methods — Research methodology details for proposals and case studies
  • design-process-methods — End-to-end process for methodology sections
  • sector-style-intelligence — Industry-specific context for proposals and case studies
  • conversion-optimization-patterns — Data for value-based pricing and case study metrics
  • micro-copy-intelligence — UX writing for documentation and component specs

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.