pikkujs/pikku-template-clone
packages/cli/skills/pikku-template-clone/SKILL.md
Standard cleanup to run right after a Pikku template is cloned or scaffolded into a new project. TRIGGER when: a Pikku template was just cloned/scaffolded (via `pikku create`, `git clone <template>`, or the user says "I cloned the kanban template / starter / template"), or the working tree still looks like an untouched template (template README, placeholder `@project/*` name in package.json). DO NOT TRIGGER when: working in an established project mid-feature, or editing the template repo itself.
$ install --global
skillsauthnpx skillsauth add pikkujs/pikku pikku-template-cloneInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 4, 2026, 6:12 AM341.5s1 file scanned
SKILL.md
- name:
- pikku-template-clone
- description:
- Standard cleanup to run right after a Pikku template is cloned or scaffolded into a new project. TRIGGER when: a Pikku template was just cloned/scaffolded (via `pikku create`, `git clone <template>`, or the user says "I cloned the kanban template / starter / template"), or the working tree still looks like an untouched template (template README, placeholder `@project/*` name in package.json). DO NOT TRIGGER when: working in an established project mid-feature, or editing the template repo itself.
- allowed-tools:
- Bash(git status *), Bash(git add *), Bash(git commit *), Bash(git rm *), Bash(git mv *), Bash(git log *)
Pikku Template Post-Clone Cleanup
Agent Operating Procedure
Run this once, right after a template is cloned or scaffolded into a new
project. The goal is to turn template scaffolding into a real project. Make the
smallest changes and land them as one focused chore: post-clone cleanup
commit, separate from any feature work.
- Replace the template README. The shipped
README.mddescribes the template, not the user's project — leaving it in place is misleading. Either delete it (git rm README.md) or rewrite it with the new project's name and purpose. Never ship a clone with the generic template README. - Keep the lockfile committed. Templates ship a committed
yarn.lock; do NOT re-addyarn.lockto.gitignore. A real project commits its lockfile for reproducible installs. The correct pattern isyarn.lockfollowed by!/yarn.lock, which commits the root lockfile while keeping generated per-unit lockfiles under.deploy/(ande2e/) ignored. - Rename template identifiers. Update
namein the rootpackage.json(and any@project/*or other placeholder names) to the real project. - Drop template-only artifacts. Remove any
TEMPLATE.md, demo docs, or placeholder content that only made sense for the template.
Do not touch generated files (.pikku/, *.gen.*) or run a full reinstall as
part of cleanup — this step is project hygiene, not a build.
Why this exists
Templates are structure-only starting points. Without this pass, clones carry a misleading README, a placeholder package name, and (historically) a gitignored lockfile — all of which leak template assumptions into a real project. Running it immediately after clone keeps every Pikku project, OSS or Fabric, starting from a clean, honest baseline.
Related Skills
pikkujs/pikku-rtl
development
VerifiedTrustedCommunity
Make a Pikku frontend work in both English (LTR) and Arabic / right-to-left languages. Direction is derived from the active locale, applied once at the document root, and the layout mirrors itself — but only if styling is written flow-relative (margin-inline-start, text-align: start, Mantine ms/me) instead of left/right. TRIGGER when: adding Arabic (or Hebrew/Farsi/Urdu), asked to "support RTL / right-to-left / bidi / mirror the layout", or writing layout styles in an app that may run RTL. Builds on pikku-i18n (an RTL language is just another locale file). DO NOT TRIGGER for backend functions or for LTR-only copy changes.
56SKILL.mdUpdated Jun 4, 2026
pikkujs/pikku-i18n
development
VerifiedTrustedCommunity
Wire i18n into a Pikku frontend (Vite SPA, Vite SSR, or Next.js app-router) with react-i18next + i18next. English by default, every user-facing string goes through a `t()` token, and additional languages are served under `/de` `/es` URL prefixes. TRIGGER when: scaffolding or editing a frontend and writing user-facing text, adding a second language, or asked to "make this translatable / use tokens / add i18n". DO NOT TRIGGER for backend functions, error messages thrown from functions, or log output.
56SKILL.mdUpdated Jun 4, 2026
pikkujs/pikku-n8n-code-translate
development
VerifiedTrustedCommunity
Use when translating an n8n Code node body into a real Pikku function body. Triggered when the user opens or points at a stub generated by @pikku/n8n-import (look for `STUB — generated from n8n Code node` in the file's JSDoc), or when the user says 'translate this n8n code', 'port this n8n code node', 'finish the codeStub__... function', etc. The stub file is a `pikkuSessionlessFunc` with a Zod input/output, a JSDoc preserving the original n8n JavaScript verbatim, and a `throw new Error('… — implement me')` body.
56SKILL.mdUpdated May 21, 2026
pikkujs/pikku-n8n-addon-map
tools
VerifiedTrustedCommunity
Use when mapping n8n integration stubs (gmailTool, slackTool, googleSheetsTool, plain gmail/slack action nodes, etc.) emitted by @pikku/n8n-import to real `@pikku/addon-*` functions. Triggered when the user points at a `<workflow>.integrations.json` manifest produced by `pikku-n8n-import`, says 'map the n8n integrations', 'wire up the gmail/slack stubs', 'replace these stubs with addon refs', or opens a stub file generated from an n8n integration node (the stub's JSDoc says `STUB — generated from n8n node "..." (type "n8n-nodes-base.<service>...")`). For n8n **Code** node stubs use `pikku-n8n-code-translate` instead.
56SKILL.mdUpdated May 21, 2026