T3 Code mapping
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 84/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown, typescript
- Domain
- documentation
Research direction
The issue points to a ready-made docs diff in the compare link and names the docs/t3-code-skill-mapping path. Start by reading the existing harness-to-board mapping entries under docs/ and compare their structure with the proposed T3 Code addition. Add the T3 Code mapping in the same format, then preview the rendered Markdown to check links and table/list formatting. Done means the T3 Code mapping is documented consistently with the other harness mappings.
Written by the indexing model from the issue text.
Description
Hey! The idea to map harness <-> board is pretty nice. I'm using T3 Code and I think it's popular enough to add that mapping too.
I can't create a PR but here's the diff (feel free to "copy" or so): https://github.com/vercel/board/compare/main...kurtextrem:board:docs/t3-code-skill-mapping?expand=1&w=1
Model used: Gemini 4 Neon (high).
- Dominant language
- TypeScript
- Stars
- 178
- Forks
- 16
- Avg merge
- 8h 44m
- Merged PRs (30d)
- 411
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vercel/board
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
Similar issues
-
kind:defect
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
mux-labs/mux-frontend#1240 ·
Maintainers usually reply within 1 day
-
area: agents-mcp priority: normal
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Wait for the IDS correction dialog to settle in the stale-audit testPossibly taken @louistrue claimed this today. Openready
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Hono path parameters with a regex pattern keep the pattern in the OpenAPI pathPossibly taken @0z5a claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
cloudflare/chanfana#400 ·
Maintainers usually reply within 1 day