Ikaleio avatar

Ikaleio

Community

@Ikaleio

22Followers
|
27Public Repos
|
8Published Skills

To infinity and beyond!

Skills Distribution
DomainUI/UX & Crea...UI/UX & Creative M.. (45%)Developer Tooling .. (30%)Growth, Marketing .. (15%)Business, Finance .. (10%)

Agent Skills by Ikaleio

Showing 8 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About Ikaleio

FAQPage Schema
What tasks can I accomplish with Ikaleio's skills?

You can automate browser interactions (navigation, form filling, screenshots, data extraction, web app testing), manage shadcn/ui components and presets, extract or create design systems via design.md, convert Notion specs into implementation plans, generate websites from design images, and enforce Simplified Technical English on technical prose.

Who are Ikaleio's skills designed for?

Frontend engineers building React interfaces with shadcn/ui and Tailwind, QA engineers running exploratory testing and bug hunts, designers codifying brand systems into design.md files, product teams turning Notion PRDs into tracked tasks, and technical writers standardizing documentation prose.

How do the browser and shadcn skills run in practice?

The agent-browser skill executes through Bash commands like 'agent-browser' or 'npx agent-browser' for programmatic web interaction, including Vercel Sandbox microVMs and AWS Bedrock AgentCore cloud browsers. The shadcn skill runs via 'npx shadcn@latest', 'pnpm dlx shadcn@latest', or 'bunx --bun shadcn@latest'.

What prerequisites do these skills require?

The shadcn skill requires a project with a components.json file or a shadcn init context. The ikadesign2 skill needs existing frontend code, a website, screenshots, or brand requirements as input. The notion-spec-to-implementation skill requires Notion PRDs or feature specs as source material.

When should the ste-writing skill be applied?

Apply ste-writing whenever substantial technical prose is produced: architecture reports, READMEs, runbooks, specifications, pull-request descriptions, release notes, and error messages. It enforces a controlled writing style in English, Chinese, or other languages, but excludes executable code, command syntax, marketing copy, and creative writing.