When to use this workflow
Use this skill to form and test a communication hypothesis from audience evidence. Begin with the decision someone is trying to make, what they currently misunderstand, and what the product can truthfully promise. Persuasive wording should make the offer easier to evaluate, not conceal constraints.
A worked example
For a pricing-page exercise, inspect whether visitors can distinguish the plans and understand what happens after selecting one. Rewrite one unclear section using concrete inclusions, limitations, and next steps. State the hypothesis: clearer scope should help the intended audience choose with less uncertainty. Keep that separate from a claim that conversion has already improved.
Decisions and common mistakes
Do not add invented scarcity, testimonials, guarantees, or performance numbers. A behavioral principle can suggest a question to investigate; it is not proof that a specific audience will respond as predicted. Compare comprehension and completion alongside clicks so an attention-grabbing treatment does not hide a worse decision experience.
What to hand off
Hand off the original copy, proposed copy, supporting evidence, and evaluation plan. Preserve material limitations in the final page. If the change requires new claims, obtain the underlying evidence before publishing rather than asking an agent to make the language sound more convincing.
Set up and try the skill
1. Start with one concrete task
Bring: Audience research, current copy, the conversion goal, and evidence supporting any claims.
First task: Choose one point of friction and draft a truthful alternative with an explicit hypothesis.
Choose a small task for “apply marketing psychology.” Provide the relevant file, screen, or brief and define what a useful result should contain. Keep the original version available for comparison.
2. Install and verify the instructions
Run this command from the project where you want the skill available. Follow the installer’s host selection, then confirm the skill appears in that host. The command is the installation method documented by the TDP repository.
npx skills add thedesignproject/agent-skills -s marketing-psychologyRead the full skill instructions for prerequisites and supported tools. Installing a skill does not automatically connect Figma or grant access to external tools.
3. Apply it with your project context
Use the starter request below with the relevant inputs attached or referenced. Confirm that the host loaded the intended skill; a matching name alone is not evidence that its instructions were applied.
4. Review the result
Check that the copy preserves informed choice; compare completion and comprehension rather than clicks alone.
Compare the output with the task’s acceptance criteria. Check factual claims, unsupported assumptions, and any changes to the interface. For code or design changes, review real states and behavior before treating the result as finished.
5. Keep what works
Save approved outputs with their source and ownership. Note which instructions helped, where the result needed correction, and what must be checked next time. Use the workflow below to connect this task to its next step.
A starter request
Adapt this example to your files, audience, and requirements.
Review this onboarding copy for this audience and goal. Explain the principle behind each change, preserve truthful claims, and propose a way to test the recommendation.
Completion checklist
- The inputs and intended result are explicit.
- Required files and tools are available in the chosen host.
- The result has been reviewed against the actual task.
- Limitations and follow-up checks are recorded.