Skip to content
Let’s chat ↗
TEAM RESOURCE / THE TDP TOOLKIT

Build your AI design assistant

Set up an AI design assistant around your critique methods, working preferences, optional references, and reusable lessons. A free setup skill for Claude Code and Codex.

How TDP uses it

Work through the questions, review the personal files, and point your agent to them in each project. Keep refining your preferences as you work.

Usage note adapted from the original TDP skills collection. Activation and available tools depend on the agent host and installed version.

Give AI context about working with you

The setup skill helps you capture critique methods, collaboration preferences, optional references, and reusable lessons. Your answers live in editable personal files, separate from the skill itself.

Keep your preferences connected to the project

Read your personal instructions alongside the project’s users, components, rules, and feature requirements. Each agent needs access to the saved files before it can use or update them.

Choose how your setup evolves

Decide whether clear preferences are saved as you work, reviewed together, or saved only when you ask. A temporary exception can stay specific to one task.

Put the resource to work

1. Start with one concrete task

Bring: An AI coding agent that can read and write files, plus your own critique methods and working preferences. A company repository and visual references are optional.

First task: Work through the setup interview, review your saved personal instructions, and point the agent to those files in a real project.

Choose one component, screen, or team workflow to improve. Gather the existing decisions and write down the question you want this resource to help answer.

2. Open the source material

Open the original guide or presentation ↗

Use the original walkthrough alongside your project. Its existing access flow remains available on the original page.

3. Apply it with your project context

Follow the material in sequence and replace examples with your own product context. Record decisions as you go so another teammate can understand why the result changed.

4. Review the result

Ask the agent to summarize your critique priorities, when it should pause, and how updates should be saved. Compare its answer with your files before starting design work.

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.

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.
CONNECT THE NEXT STEP

Use it in a workflow

Explore the five TDP skill workflows ↗