techtankto/techtank-site

🐠 TechTank Toronto - Modern Website Redesign

5Stars on the repository
14Mods indexed here, across every type
7d agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

accessibility

01

techtankto/techtank-site

Skill Claude CodeCodex

Web accessibility baseline (WCAG 2.0 AA / AODA) for landmarks, keyboard operability, focus states, motion, and contrast. Use when building or reviewing UI components, pages, navigation, overlays, or any self-starting animation/motion in a web frontend.

not rated 5 7d ago A 60 tokens original MIT

claude

02

techtankto/techtank-site

Skill Claude CodeCodex

Claude Code repo hygiene — keeping CLAUDE.md a symlink to AGENTS.md and gitignoring Claude Code's local-only state. Use when setting up a repo for Claude Code, or auditing one that already has a CLAUDE.md and/or AGENTS.md.

not rated 5 7d ago A 58 tokens original MIT

components

03

techtankto/techtank-site

Skill Claude CodeCodex

House style for authoring, shaping, and styling React/shadcn components (file skeleton, CVA variants, this repo's flat ui/layout organization, layout shell). Use when adding, refactoring, or reviewing a component in this project.

not rated 5 7d ago A 51 tokens original MIT

data

04

techtankto/techtank-site

Skill Claude CodeCodex

Where content and state live in a typed frontend (constants/ as source of truth, state discipline, date and media handling). Use when adding site copy/content, deciding where data or state should live, or handling dates and media entries.

not rated 5 7d ago A 49 tokens original MIT

git

05

techtankto/techtank-site

Skill Claude CodeCodex

Git workflow standards — Conventional Commits, branch naming, the no-AI-attribution rule, and how to review a PR. Use when creating branches, writing commit messages, opening PRs, reviewing a PR, or the user asks how a change should be recorded in git.

not rated 5 7d ago A 58 tokens original MIT

nextjs

06

techtankto/techtank-site

Skill Claude CodeCodex

Next.js App Router conventions — runtime/language foundations, server-vs-client components, static generation, metadata, and folder structure. Use when scaffolding a Next.js app, adding a route/page, or deciding how a piece of code should be organized in a Next.js + TypeScript codebase.

not rated 5 7d ago A 63 tokens original MIT

performance

07

techtankto/techtank-site

Skill Claude CodeCodex

Frontend performance discipline — LCP budget, lazy-loading, vector assets, motion budgets, and font loading. Use when adding images/media, animation, custom fonts, or reviewing a page for load/interactivity regressions.

not rated 5 7d ago A 45 tokens original MIT

process

08

techtankto/techtank-site

Skill Claude CodeCodex

Project delivery methodology for planning and initial implementation — the PRD pipeline, division of truth between repo/design tool/GitHub, and milestone kinds. Use when planning work, cutting milestones, deciding what belongs in which doc, or setting up a delivery process for a new project.

not rated 5 7d ago A 57 tokens original MIT

seo

09

techtankto/techtank-site

Skill Claude CodeCodex

SEO baseline — root/route metadata, Open Graph and Twitter cards, crawlable server-rendered content. Use when adding metadata to a page/route, sharing links, or reviewing whether content is crawlable.

not rated 5 7d ago A 44 tokens original MIT

testing

10

techtankto/techtank-site

Skill Claude CodeCodex

Testing strategy — the testing pyramid (unit base, integration middle, e2e few), when to reach for each layer, and keeping the runner green. Use when deciding what kind of test to add, setting up a test runner, or reviewing a PR that adds test coverage.

not rated 5 7d ago A 58 tokens original MIT

vscode

11

techtankto/techtank-site

Skill Claude CodeCodex

Editor-session hygiene for this repo. Use when the repo directory has just been moved or renamed, so the open editor is pointed at a stale path.

not rated 5 7d ago A 33 tokens original MIT

writing

12

techtankto/techtank-site

Skill Claude CodeCodex

House style for project prose — docs, plans, PR and commit bodies. Declarative voice, load-bearing sentences, rationale inline, structure and mechanics rules. Use when writing or editing documentation, PR descriptions, commit bodies, or standards/process docs (not product/site copy, which is the design's voice).

not rated 5 7d ago A 63 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: