How to Build a Penpot Component Inventory from a Brief

Component lists invent checkout modals. Names only from the allowlist.

The matching generator is the Penpot Component Inventory from a Brief (No Fake UI Screenshots) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).

Map Brief needs to Allowed names first

Build a Penpot component inventory and naming table from a product brief. Never invent brand logos, fake UI screenshots, or unlisted components. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.

Paste these fields before you hit run:

Product brief (surfaces, must-have components): [Brief]
Allowed component names (exact list or NONE): [Names]
Naming convention I lock (or NONE): [Convention]
Penpot version or file note I lock (or NONE): [Version]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Max components: [Max]

That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.

Keep status draft until the file exists

Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.

Walk the Generate list in order:

1. Honesty ledger: Brief items, Names status, Convention status, Version status, Lang, Max. Forbidden: invented logos, fake screenshots, unlisted components.
2. Name map: each Names entry to Brief need or OTHER.
3. Inventory table: component, purpose from Brief, status draft. If Names is NONE, list Brief needs as NEED ONLY with name NOT IN INPUTS.
4. Build order: up to Max items; dependencies only if Brief states them.
5. Refuse list: invented brand marks, PNG mock screenshots, Figma-only plugins, unlisted components.
6. Diff notes: Banned/Never cuts. OTHER names stay leftover.
7. Version note: quote Version or write unknown.
8. Compliance pass: Banned/Never hits. Component count vs Max. Gaps list of five. Format as Format.

If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.

Refuse logos and fake PNG screenshots

Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.

Honor the constraints as hard stops, not vibes:

• Penpot inventory from Brief and Names only. Not Storybook, not tokens JSON, not fake UI art.
• Never invent logos, screenshots, or unlisted components.
• Stay at or under Max components.
• No emojis.

When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.

Print component count against the max

Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.

Tags on the card (penpot component inventory, no fake ui screenshots, design system brief) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.

Fill the card, then run

Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.