AI Agent Skills
Tkeron ships with AI agent skills — Markdown files (SKILL.md) that an AI coding agent can read to understand the entire tkeron workflow: CLI, folder structure, file types, components, the build lifecycle, testing, best practices and common pitfalls.
Drop them into any project with a single command:
tk skills
This installs the bundled skills into ./skills/. Point your agent's skill loader at that directory (or copy the folders to wherever your agent expects them).
Command
tk skills [target] [--force] [--dry-run]
| Argument | Default | Description |
|---|---|---|
target | ./skills/ | Directory where skills are installed |
--force | false | Overwrite existing files without prompting |
--dry-run | false | Show what would be installed without writing anything |
Examples:
tk skills # install into ./skills/
tk skills agent-skills # custom target directory
tk skills --force # overwrite existing files
tk skills .github/skills # drop directly into a Copilot-friendly folder
tk skills --dry-run # preview without writing
Bundled Skills
tk skills installs the following Markdown skill files:
| Skill | Covers |
|---|---|
tkeron | Core CLI, build lifecycle, file types, IDE & testing setup |
tkeron-components | .com.html, .com.ts, .com.md, .pre.ts, .post.ts |
tkeron-organization | Project layout, naming, when to componentize |
tkeron-patterns | Patterns, anti-patterns, security, performance |
tkeron-testing | getBuildResult() API, recipes, deterministic tests |
tkeron-troubleshooting | Common build errors, dev server recovery, diagnostics |
Each skill is a self-contained SKILL.md with a YAML frontmatter description and instructions.
Auto-detection
tk skills detects the AI environment of your project and applies environment-specific transforms automatically:
- GitHub Copilot (
.github/) — installs as.github/skills/<name>/SKILL.md - Cursor (
.cursor/) — addsalwaysApply: falseto the frontmatter - Claude (
.claude/) — installs directly with no transforms - Generic — drops files into the chosen target directory as-is
If no environment is detected (or you pass an explicit target), files are installed verbatim into the target directory.
Why Skills Instead of an MCP Server?
Earlier versions of tkeron shipped a tkeron-mcp server that exposed documentation via the Model Context Protocol. As of v6, the MCP server has been removed in favor of tk skills.
Skills are simpler, work with any agent that understands plain Markdown, and live inside your project so they:
- Are versioned alongside your code
- Work offline, without an extra running process
- Can be edited or extended per-project
How Agents Use Them
After installation, the agent reads the relevant SKILL.md files on demand. Skills describe:
- ✅ The full CLI (
tk init,tk dev,tk build,tk skills) - ✅ How components and pre/post-rendering work
- ✅ Project organization conventions
- ✅ Required patterns (escapeHtml, attribute validation, fetch with timeout)
- ✅ Anti-patterns to avoid (event listeners in
.com.ts, browser APIs at build time, etc.) - ✅ How to write tests with
getBuildResult() - ✅ How to recover the dev server and diagnose build failures
Next Steps
- Overview — Learn what Tkeron is
- Getting Started — Start using Tkeron
- Best Practices — Patterns and anti-patterns
- CLI Reference — All commands