Design competition entry
Skill Evan-Joseph/agent-workflow-skills/skills/design-competition-entry
Reusable Agent Skills for research figures, frontend refreshes, design workflows, model consultation, social research, and security asset searches.
npx -y skills add Evan-Joseph/agent-workflow-skills --skill design-competition-entryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Manage a design competition entry from brief verification to deliverable planning. Use when an agent must check official rules, choose the correct deliverable branch, define a concept, write image or layout prompts, review drafts, and prepare submission assets.
SKILL.md
3.8 KB, 763 tokens by cl100k_base, as published. Nobody here has run it
Design Competition Entry
Use this skill for design competition work that has rules, categories, deliverables, prompts, drafts, and final submission files.
Do not start by making images. Start by verifying the brief and choosing the right deliverable branch.
When to use
Use it when the task involves:
- reading or re-checking a competition brief
- choosing a category or deliverable type
- planning product, poster, script, spatial, or video materials
- writing prompts for image or layout generation
- reviewing drafts against rules and submission needs
- preparing final assets for a competition platform
Do not use it for a one-line copy edit or a single standalone image prompt.
First pass
Always output these four blocks before creative work:
- Official rules snapshot
- competition name
- verification date
- official sources
- confirmed requirements
- open questions
- Branch decision
- selected branch
- reason
- branches not used
- Current deliverable
- what will be produced now
- what it depends on
- Next step
- one concrete next action
If official rules are missing or incomplete, continue with clearly marked assumptions and open questions. Do not invent final requirements.
Branches
Choose one branch:
- Product or poster board: visual identity, product set, application set, final board.
- Script or digital media: concept, story, scene structure, key visuals, final text or media package.
- Environment or spatial design: site assumption, movement path, zones, materials, views, explanation board.
- Video or virtual production: prompt, script, storyboard, shot plan, production workflow, technical note.
If the task does not fit these branches, say so and define a task-specific branch before continuing.
Workflow
0. Verify rules
Check the latest official source. Record:
- exact competition or track name
- dates
- category definitions
- deliverables
- size, format, duration, resolution, and file limits
- logo or organizer requirements
- prohibited content or common disqualification risks
Use exact dates instead of "today", "this year", or "next week".
1. Set up a working structure
For new entries, create or ask for a simple structure:
00-sources/
01-brief/
02-references/
03-prompts/
04-drafts/
05-submission/
Keep raw sources, references, prompts, drafts, and final assets separate.
2. Read the brief
Summarize:
- theme or problem
- target audience
- judging priorities
- required deliverables
- format constraints
- clear risks
3. Choose and narrow the concept
Pick one direction. A usable direction states:
- the source idea or cultural/technical basis
- the intended use or experience
- why it fits the track
- what has been ruled out
Do not keep five weak concepts alive just to look comprehensive.
4. Define deliverables before prompts
Before writing generation prompts, define the object or page:
- category
- structure
- number of components
- material or medium
- dimensions or aspect ratio
- required text
- forbidden text
- what the result must not turn into
Read references/prompt-rules.md before writing image or layout prompts.
5. Review drafts
Review against:
- official rules
- branch fit
- category recognizability
- practical use
- visual hierarchy
- text whitelist
- source/reference consistency
- final submission constraints
Use references/review-checklist.md before regenerating or submitting.
What ships with it: 3 files
4.6 KB alongside SKILL.md
agents/
- openai.yaml226 B
references/
- prompt-rules.md2.5 KB
- review-checklist.md2.0 KB