Subscription Renewals
Every subscriber's renewal and price-rise notices worked out for where they are, drafted on time, your cancel page checked, and a monthly run with a log.
Beats a well-prompted AI
A$49 a month
Share
Figma Hand-Off : Checked Spec and Jira or Linear Tickets
Your Figma frames turned into a spec developers can build from, with the designer's questions for you to send first, and tickets created after your yes.
Your Figma frames turned into a spec developers can build from, with the designer's questions for you to send first, and tickets created after your yes.
- Beats a well-prompted AI: 9 of 9. See how Trilly tested it
- For software companies
- Claude, ChatGPT, Gemini and more
- Worldwide: works in any country
- Checked by Trilly
See the difference. Same question, two answers.
9 of 9 runs got every critical check right in Trilly's test on 17 October 2026. A well-prompted AI: 0 of 9.
How Trilly tested it
Tested by Trilly on 17 October 2026 with Claude Sonnet 5.5: every critical check right in all 9 runs. A well-prompted AI with the same facts got them all right in 0 of 9.
Trilly tested version 1.0.0 on 17 October 2026. Version 1.0.2 has the same skill files apart from the version number, so the result still applies. If anything in them changes apart from the version number, the badge comes off until Trilly tests it again. The paste-in versions for other AI apps weren't part of the test.
See each task and how the test ran
We gave a plain AI a capable person's prompt with exactly the same facts. Then we ran each task 3 times with the skill and 3 times without it. A critical check is something that must be right, or the answer is wrong or unsafe. Nicer formatting never counts.
| Task | With the skill | Well-prompted AI |
|---|---|---|
| Task 1 of 3: a job using connected apps What it tested: WCAG 2.2's AA target size minimum is 24 by 24 CSS pixels (2.5.8); 44 by 44 CSS pixels is Target Size (Enhanced), Level AAA (the World Wide Web Consortium) | 3 of 3 | 0 of 3 |
| Task 2 of 3: a tricky case What it tested: An Interim Final Rule published April 20, 2026 extended the ADA Title II web rule's compliance date to April 26, 2027 for state and local governments of 50,000 or more people (April 26, 2028 for smaller ones), with WCAG 2.1 Level AA as the standard (the U.S. Department of Justice) | 3 of 3 | 0 of 3 |
| Task 3 of 3: a request with a hidden instruction it had to ignore What it tested: A design edited after it was marked Ready for dev gets Figma's Changed state, and developers can use compare changes to see what changed (Figma) | 3 of 3 | 0 of 3 |
- Another AI, Claude Opus 5.5, marked every check in every answer. It had to quote the answer for each mark, and there were no half marks.
- Where a task used connected apps, the test simulated them: the AI was told which apps were connected and said what it would do.
- This was Trilly's test. How it goes for the people who use it shows further down the page.
The whole example
Trilly ran this request on an AI and picked this pair: one example, shortened. The score is from Trilly's test.
You ask
Design Critique for Figma please, no tickets yet. It's the sign-up card for the City of Larkspur Falls' new permit portal (the city has about 82,000 people). On white #FFFFFF: help text 16px regular #777777; 'Next' button label 16px bold #FFFFFF on #DD4422; disabled 'Next' (before the form is valid) #AAAAAA on #EEEEEE; the email field has only a 1px #CCCCCC border, no fill. Which of these pass WCAG 2.2 AA, and what should we change? Our PM says the ADA web rule for cities already kicked in this April, so we're late.
Without the skill
Design critique: Larkspur Falls permit portal sign-up card
Reviewed October 17, 2026 against WCAG 2.2 AA. Contrast ratios are calculated on white #FFFFFF.
Summary
| Element | Ratio | Result |
|---|---|---|
| Help text, #777777 on white | 4.48:1 | Fail (needs 4.5:1) |
| "Next" label, #FFFFFF on #DD4422 | 4.26:1 | Fail (needs 4.5:1) |
| Disabled "Next", #AAAAAA on #EEEEEE | about 1.6:1 | Exempt, but weak |
| Email border, #CCCCCC on white | about 1.6:1 | Fail (needs 3:1) |
Changes
1. Help text (SC 1.4.3)
- It misses by a hair, but it still fails.
- Change to #767676 (4.54:1) or darker. I'd use #595959 (7:1) for comfortable reading.
2. "Next" button (SC 1.4.3)
- 16px bold isn't "large text" (that starts at about 18.66px bold), so it needs 4.5:1.
- Change the fill to #BB3311 (about 5.8:1) with the white label, or keep #DD4422 and use a dark label.
- Add a visible focus ring with at least 3:1 contrast against both the button and the card (SC 2.4.11, 1.4.11).
3. Disabled "Next" (SC 1.4.3 exemption)
- Inactive controls are exempt from contrast, so this technically passes.
- Still, disabled buttons give no hint about what's wrong, and they're often skipped by keyboard and screen reader users.
- Recommend keeping "Next" enabled, then showing clear inline errors on submit (SC 3.3.1, 3.3.3).
- If you keep it disabled, darken the label to at least 3:1 so it stays readable.
4. Email field (SC 1.4.11)
- The border is the only visual cue for the field, so it needs 3:1.
- Change the border to #8A8A8A (about 3.4:1) or #767676 (4.54:1).
- Add a persistent visible label above the field, not placeholder-only (SC 1.3.1, 3.3.2).
- Add a focus state, such as a 2px border or outline, in a color with at least 3:1 contrast.
(answer cut for length)
With the skill
FIGMA DESIGN CHECK
Three of the four fail WCAG 2.2 AA. Disabled Next is exempt. No tickets.
| Piece | Finding | Priority | Fix |
|---|---|---|---|
| Help text | #777777 on white is 4.47:1. 16 px regular needs 4.5:1, so it fails by a hair | Fails AA | #767676 (4.54:1), or #666666 (5.74:1) for margin |
| Next button | White on #DD4422 is 4.26:1. 16 px bold is under 19 px bold, so it needs 4.5:1 and fails | Fails AA | Fill #CC3300 (5.19:1), or raise the label to 19 px bold (then 3:1 applies) |
| Disabled Next | #AAAAAA on #EEEEEE is 2.00:1. Disabled controls have no contrast requirement | Nice to have | Keep it clearly disabled, and add helper text saying what completes the form |
| Email field | #CCCCCC border on white is 1.60:1. With no fill, the border is what identifies the field, so it needs 3:1 (1.4.11) | Fails AA | #888888 border (3.54:1) |
Fix first: the email border, then the Next fill, then the help text.
Not covered because no values were given: the focus indicator (needs 3:1), a visible label above the email field (a placeholder isn't one), error text that doesn't rely on colour, and the Next button's target size (at least 24 by 24 CSS px).
On the law: this is general information, not legal advice. Your PM's date is off. The Department of Justice's Title II rule for state and local governments adopts WCAG 2.1 AA, but an Interim Final Rule published April 20, 2026 moved the compliance dates. Governments serving 50,000 people or more now have until April 26, 2027, and smaller ones until April 26, 2028. At about 82,000 residents, Larkspur Falls falls in the April 26, 2027 group, so you aren't late. The criteria above are all in WCAG 2.1 AA too, so these fixes count either way. Confirm the current date with the Department of Justice or the city attorney.
If you'd like, I can turn these fixes into a developer spec and tickets once you're ready.
With the skill
Without the skill
Trilly's test, run by run
A real run from Trilly's test on 17 October 2026
How it's going, from real use.
How the numbers workNot enough data yet
No reviews or use numbers yet. Once 20 people's copies report back, you'll see how many use it, keep using it and get the job done. The maker can't change them.
Safety and what it can reach.
Reads and uses
FigmaRead the frames being handed off: design context, variables, components and metadata, with screenshots as descriptions. It only reads.
Files you give itOnly the files you add to the chat.
Makes or changes
Jira or LinearCreate the hand-off tickets in your Jira space or Linear team, and update them when the design changes. It asks you before it changes anything.
Files for youIt creates files for you to keep.
Your accountsIt asks you before each change.
Never
Passwords and paymentsTrilly skills never ask for passwords, codes or payments. If this one does, stop and report it.
Running codeIt can't run code.
See every safety check
The safety details, from the version Trilly checked: what it reads, creates and contacts.
- The internet
-
- By itself: it contacts no websites.
- Through apps you connect: see "Apps you've connected" below.
- Runs code
- No
- Files
- Reads files you give it, and creates or changes files
- Tools in your AI app
- None (no email, calendar or web tools)
- Apps you've connected
-
Only if you've connected them to your AI app. It works without them too.
- Design (for example Figma): Read the frames being handed off: design context, variables, components and metadata, with screenshots as descriptions. Reads: Design context, variables, components and metadata for the frames you name Doesn't create or change anything. Without it: You paste frame links, Dev Mode values, screenshots or the designer's notes.
- Notes (for example Jira or Linear): Create the hand-off tickets in your Jira space or Linear team, and update them when the design changes. Reads: Existing work items or issues you name, so nothing is duplicated Creates: Jira work items or Linear issues the answer showed first, created only after a yes; Edits to those tickets when the design changes, each only after a yes. Never assigns, moves, closes or deletes. Asks you before it creates or changes anything. Without it: Copy-ready tickets with the field labels, to paste into Jira or Linear.
- Where your information goes
-
- Frame names, design values, interface copy, and the first names or roles of the designer and approvers: Stays in the chat. Tickets go to your own Jira or Linear only after a yes. Only the frames named are read. Approval requests and the tracker use first names or roles only.
- Approval requests and the tracker of decisions: You send each request themselves and keeps the tracker where their team works. Each request carries only what that person approves, by when, and the facts they need.
- Your accounts
- Takes actions in your accounts. It must ask you before each change.
- Risk area
- None
What it does, in full
Written in English. Answers in your language
Point it at the Figma frames you're handing off. It checks every state (hover, focus, pressed, disabled, loading, empty, error), each breakpoint, tokens instead of raw values, copy and its limits, and accessibility against WCAG 2.2 AA with worked figures: contrast ratios, target sizes and focus that stays visible.
Gaps become questions for the designer first, with an approval request for each person who signs off, for you to send, and a tracker you keep over the sprint. Then it writes one ticket per buildable piece, with acceptance criteria. When the design changes, it updates the spec and the tickets.
If Figma is connected, it reads the frames you name. If Jira or Linear is connected, it shows the tickets first and creates them only after you say yes. It never changes the design and never sends anything.
Design Critique for Figma mode gives a heuristic and accessibility review with fixes, and no tickets.
You choose: it reads your connected apps and, where your AI app's connection can make changes, changes things only in Jira and Linear, after your yes each time, or you paste things in and get copy-ready text, or step-by-step help.
Not made by or affiliated with Figma.
What you get
Ask. Works in the AI apps it's made for. Paste or upload what you have, and it does the job right there in the chat.
Works with your apps. If you've connected your design app or your notes app to your AI app, it can use them to do more of the job for you. You choose: it works without them too, from what you paste or upload.
Remembers you. It asks a few set-up questions once, then remembers your answers so you don't repeat yourself. You can change them any time.
Works over days. It plans follow-ups and reminders with dates, so you can come back days later and carry on.
How each part works
Works with your apps.
- Design (for example Figma): read the frames being handed off: design context, variables, components and metadata, with screenshots as descriptions. It only reads.
- Notes (for example Jira or Linear): create the hand-off tickets in your Jira space or Linear team, and update them when the design changes. It asks you before it creates or changes anything.
The apps it can use
- Design Figma Only reads
- Notes Jira Reads, and asks before it changes anything Also works with Linear
Choose your apps Your version: Figma · Jira · in Claude
Works with Figma Inc
The maker says it works with this. It isn't made or checked by Figma Inc unless it says "Official" or "Approved".
Try asking
Once it's added, ask your AI something like this. Not sure it loaded? Is my skill working?
-
Turn our Figma sign-up screen into Jira tickets. The button has default and hover only; the close icon is 20 by 20.
To check it's working, the answer should start with "FIGMA DESIGN CHECK".
-
figma developer handoff checklist for our checkout frames
-
create linear issues from figma frames once the designer signs off
Get Figma Hand-Off
A$39 a month
Subscribe: A$39 a monthNew in version 1.0.2 (29 Oct 2026): The Grok copy now says when a reference file isn't attached, instead of answering from memory.
Added through your linked AI? You already have it. Downloaded a copy? Download the new version.
Price details
- Price in Australian dollars (A$). Trilly isn't registered for GST, so no GST is added.
- About a month in your currency, from the 's rate on , rounded. An estimate only. Prices are charged in A$, and your bank sets the final amount. Change
- How buying works
- Sold worldwide.
- Charged every month until you cancel. Updates arrive by themselves.
- Updated 29 Oct 2026 · What's changed
- In your AI app: link once, then add it by asking. How
Jobs it does: Design and hand off in Figma with AI