Skills

How generaltranslation.com is built and changed in gt-cloud's apps/landing. Use when working on any page, doc, blog post, route or build of the GT website, together with gt-cloud's own gt-landing skill, which owns the file map.

How to work in Prototemplate, Kevin's hub and wiki for General Translation work. Use when changing anything in the Prototemplate repository, when adding a route, document or skill to it, or when building on it from another project.

How General Translation keeps visual surfaces fast with no change to how they look. Use when a page or animation lags, before shipping a shader, canvas or heavy component, and when Kevin asks for Lighthouse or performance work.

The page grammar for General Translation landing and marketing pages. Use when designing, building or reviewing a landing page, a home band, or a pricing, enterprise or careers page.

Kevin's taste for General Translation work and the review he applies to it. Use when designing or polishing any GT surface, when Kevin says something looks bad, busy or ugly, and before showing him design work.

The General Translation identity as rules. Use before making anything that carries the GT brand (a page, a slide, a graphic, a film, an email or a social image), when choosing a face, weight, tracking or color, when placing a GT mark or a third-party logo, and when reviewing a surface against the brand.

How the General Translation brand deck in Prototemplate's deck/ folder is built and edited. Use when adding or editing a slide, rebuilding or checking the deck, reviewing a slide lane's work, writing another GT presentation, or borrowing the deck's grammar for another surface.

How a General Translation design exploration runs from research to one landed design. Use when Kevin asks for options, versions, variations, directions or "try N approaches", when he links a post or product to learn from, and when converging a design toward his pick.

Every lint and gate that holds General Translation's design and copy rules, what each catches, where it runs and how to fix a failure. Use before committing in either repository, when a lint or a build gate fails, or when Kevin asks for a new rule to be enforced.

The motion rules General Translation work follows on the web and in films. Use when animating anything for GT (a landing band, a diagram line, a dashboard or sign-in transition, a Lottie figure, a scroll story or a film scene) and when reviewing motion someone else built.

How General Translation's blog and brand graphics are made with Prototemplate's graphics/ toolchain. Use when illustrating a blog post, a launch or a feature with real product crops, when drawing the GT docs, or when making any still GT artwork.

General Translation's 1-bit material and its artifact pictures. Use when adding a dithered field, picture, cover or texture to any GT surface, when choosing or tuning a studio preset, or when cutting, replacing, crediting or reviewing a mood picture in Prototemplate or gt-cloud.

How General Translation films are made in Prototemplate's motion/ folder with HyperFrames. Use when planning, scripting, building, critiquing or rendering a GT film, trailer, sting, showreel, promo or demo GIF, or when reviewing one against Kevin's standard.

How General Translation diagrams are drawn. Use when drawing a flow, an architecture, a stack, a before and after or a timeline for a page, a slide, a post graphic or a film, or when reviewing a figure's junctions and labels.

The General Translation isometric family. Use when drawing, animating or reviewing any isometric figure for a GT page, slide, graphic or film.

The components General Translation work reuses before writing new ones. Use when building or reviewing UI in gt-cloud or Prototemplate, or before adding a component.

How General Translation apps run locally so Kevin can review and try them. Use when starting, restarting or debugging a local server for GT work, when Kevin asks to see or try something locally, or when setting up a new machine or worktree.

How to prove General Translation work is done before saying so. Use before reporting any fix or feature as done, when Kevin says something is still broken, and when closing a round.

How General Translation work moves from a worktree to main. Use when committing, opening, describing or updating a PR, answering Greptile or Bugbot, restacking after a merge, or landing work in gt-cloud or Prototemplate.

How to report to Kevin during and after General Translation work. Use when ending every turn that changed something, when Kevin asks "show me", "is it on main", "give me my PR list", "what did you do" or "what do you need from me", and when a round produces decisions for him.

How General Translation work runs across many agents and over long autonomous runs. Use when planning or running a workflow, spawning subagents or task chips, writing a brief or handoff for another agent, or resuming work after an interruption.