# Try Theo’s Council skill on your own app

Download the workshop planner before and after its redesign, then use the same prompt to ask three reviewers what they would change in your app.

[HTML](https://lukejbyrne.com/library/guides/h5q5hmhlhes/)
Content language: en
Author: Luke Byrne
Video published: 2026-11-17
Guide published: 2026-11-17

[Watch the video](https://www.youtube.com/watch?v=h5q5hMHLHEs)
Video language: English

- [Download both planners, screenshots and the setup prompt](https://lukejbyrne.com/library/downloads/theo-council-planners.zip)
- [Get Theo’s Council skill](https://github.com/t3dotgg/tstack/tree/main/skills/council)
- [Watch Theo’s original design review](https://www.youtube.com/watch?v=xq0eB8vxeqk)

## Give the reviewers a working copy

Open a copy of your project in T3 Code. Copy the SKILL.md file from Theo’s Council repository into .claude/skills/council/SKILL.md in that project. Start a fresh Claude thread, ask it to use Council and list the reviewers it can actually reach. Luke used Claude Opus, Codex and Gemini through OpenRouter. Your available models depend on the providers you have connected.

1. Download and unzip the planner pack. Open before/index.html in your browser, or use a copy of your own app.
2. Give the agent setup-prompt.txt from the pack. Replace the tested model names and app details with your own.

## Ask about one decision a visitor has to make

The planner lets a workshop organiser shorten a session to fit its target time. Someone new to the page might hesitate to press Fit. Would it immediately shorten every segment, including ones they wanted to protect? Give each reviewer the same code and the same desktop and phone screenshots. Ask them to point to a control a new visitor might hesitate to use. Keep the reviewers read-only and give the editor one pass to make justified changes.

## Check the change on a phone

Open after/index.html and compare it with the original. The stronger input outlines and the hint about previewing changes make Fit easier to understand. On a 390-pixel-wide phone, the larger action buttons leave about 145 pixels for a session title, down from roughly 270. Try typing a longer name and judge whether you would keep the layout.

## Give all three reviewers the same second look

Show the matched before and after screenshots to the same reviewers. Claude and Codex noticed the narrower title. Gemini liked the bigger buttons and put them beneath the title in its review, although the screenshot shows them beside it. Check each finding against the image, then try Fit and Undo yourself. Luke’s next brief would keep the bigger buttons and give the session name room again.

## The takeaway

Choose the next edit by trying the task that got harder. The longer session name gives the editor a concrete phone layout to fix.

## Workflow resources

- [lukejbyrne.com](https://lukejbyrne.com/library/downloads/theo-council-planners.zip)
- [github.com](https://github.com/t3dotgg/tstack/tree/main/skills/council)
- [youtube.com](https://www.youtube.com/watch?v=xq0eB8vxeqk)

## Chapters

- [0:00 Theo’s Council: three models, one edit](https://www.youtube.com/watch?v=h5q5hMHLHEs&t=0s)
- [0:41 Setting up Council in T3 Code](https://www.youtube.com/watch?v=h5q5hMHLHEs&t=41s)
- [1:40 The brief and the app](https://www.youtube.com/watch?v=h5q5hMHLHEs&t=100s)
- [2:22 Before and after](https://www.youtube.com/watch?v=h5q5hMHLHEs&t=142s)
- [2:57 What the reviewers caught](https://www.youtube.com/watch?v=h5q5hMHLHEs&t=177s)
- [3:27 Function check and next steps](https://www.youtube.com/watch?v=h5q5hMHLHEs&t=207s)

## Sources and limitations

This was one planner, three reviewers, two rounds and one edit pass. The scores were subjective. The test did not measure accessibility compliance or provider costs.

[Original video](https://www.youtube.com/watch?v=h5q5hMHLHEs)
