tkt
Community@tktcorporation · Japan
tkt provides 17 skills spanning pull-request review loops, autonomous code implementation, game design analysis, data-backed PRD authoring, and Japanese technical writing standards.
Agent Skills by tkt
Showing 19 vetted skills indexed across 3 GitHub repositories.
tktcorporationui-ux-pro-max
Generates design system recommendations by searching UI/UX style, color, and typography databases.
tktcorporationstructured-doc-writing
Writes long research-based Markdown documents through staged brief, evidence, outline, section, and review artifacts.
tktcorporationfunctional-ddd
Embeds domain knowledge into types and data using functional domain-driven design.
tktcorporationpr-review-loop
Repeats deep review and root-cause fixes on branch diffs until findings converge.
tktcorporationpr-first-reader-check
Inspects pull request titles, descriptions, commits, and comments for jargon and readability issues.
tktcorporationpr-deep-review
Reviews pull request diffs with surrounding code context across four technical lenses.
tktcorporationdot-line-design
Designs and reviews game mechanics using dot-connection and foreshadowing principles.
tktcorporationgame-design
Analyzes game codebases and proposes prioritized improvements to game design and fun.
tktcorporationdata-driven-prd
Generates PRD skeletons from user interviews and fills gaps with data from BI tools and email platforms.
tktcorporationpackage-upgrade
Upgrade npm and Cargo dependencies while auditing vulnerabilities and minimizing override debt.
tktcorporationevergreen-writing
Applies evergreen documentation principles when writing Markdown docs and code comments.
tktcorporationprd-review
Review PRD documents against eight quality criteria and output structured feedback.
tktcorporationtechnical-writing-style
Reviews and rewrites Japanese technical documents against paragraph, argumentation, and style norms.
tktcorporationpr-impact-review
Review pull request diffs for user value impact and product quality from a PdM perspective.
tktcorporationupstream-fix
Identify and plan upstream root-cause fixes across multi-module data flows.
tktcorporationautonomous-dev
Implements code changes autonomously through test-first development and iterative self-review.
tktcorporationfaithful-doc-writing
Record user statements verbatim into structured document drafts.
tktcorporationui-craft
Implement UI components using reference libraries and design tokens.
tktcorporationui-design-research
Conduct parallel web searches and synthesize findings into UI design recommendations.
Frequently Asked Questions About tkt
FAQPage SchemaWhat tasks can I accomplish with tkt's skills?▼
You can run iterative PR review-and-fix loops, deep four-perspective code reviews, autonomous feature implementation with self-review and tests, dependency upgrades with vulnerability remediation, game design analysis, data-backed PRD creation and review, and Japanese technical writing checks for READMEs, design docs, and PR descriptions.
Who are the target users of these skills?▼
Software engineers handling pull requests and package maintenance, product managers validating PRs against user value and issue intent, game designers improving mechanics and foreshadowing, and technical writers producing Japanese PRDs, Wiki articles, and design documents.
How do the PR review skills work together in practice?▼
pr-deep-review examines diffs plus surrounding callers, similar implementations, and tests across spec, correctness, quality, and design; pr-impact-review judges user value from a PdM perspective; pr-first-reader-check removes jargon and readability issues; pr-review-loop repeats review and upstream-fix cycles until findings converge.
What prerequisites or dependencies do these skills require?▼
Skills operate on local Git branch diffs, Markdown files, and codebases using npm/pnpm or Cargo. data-driven-prd additionally expects access to email delivery platforms, BI environments with SQL execution, and code repositories to fill PRD placeholders with measured data.
How does the package-upgrade skill handle security risks?▼
It prioritizes patching vulnerable packages first, accounts for supply-chain attack risks such as Shai-Hulud-style worms, and treats pnpm.overrides and [patch.crates-io] entries as debt—avoiding new overrides and evaluating whether existing ones can be removed in the same pass.