T3 Code mapping

Open Beginner friendly
#786 0 comments 0 reactions 0 assignees View on GitHub

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vercel/board

All issues in vercel/board

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.