project ployglot project scafford

Security Community

Skill notes

When to use this skill

Starting a new library and you want it to have TypeScript + Python surfaces from day one with parity enforced by tests, not vibes. Porting a single-language library to a twin (e.g. you have the TS but want the Python twin) and want the cross-language scaffolding — SPEC.md, parity fixtures, examples/{sdk,api}/, root Makefile —

Reference structure

The canonical layout this skill produces: See references/reference-structure.md for the field-by-field inventory.

Placeholders

Templates use these placeholders. Resolve every one before writing: Placeholder · Meaning · Example <slug> · Kebab-case package name (used for npm + PyPI names) · my-lib <snake_pkg> · Python module directory / import name · my_lib <scope> · Optional npm scope (drop for a flat name) · @your-org or empty

Step 1 — Resolve scaffold parameters

Accept $ARGUMENTS of the form <slug> [--scope @your-org] [--ts-only|--py-only|--both] [--dry-run]. If <slug> is missing, ask via AskUserQuestion. Validate it is kebab-case (^[a-z][a-z0-9-]*$); reject otherwise with a clear error. Derive <snake_pkg> from <slug> (s/-/_/g).

Step 2 — Inspect the working directory

Run Glob on the cwd. If the directory is empty (or contains only .git/, LICENSE, README.md), proceed to a fresh scaffold. If packages/ts/ or packages/py/ already exist, do not overwrite. Walk the layout in references/reference-structure.md and report missing files — write only the missing ones, leaving existing

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Security
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js · Python
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview project-ployglot-project-scafford.preview
# Step 5 — Write parity + examples scaffolding

| Source | Target | | -------------------------------------------- | --------------------------------------- | | `tests-parity/fixtures.json` | `tests/parity/fixtures.json` | | `examples/README.md` | `examples/README.md` | | `examples/sdk-README.md` | `examples/sdk/README.md` | | `examples/api-README.md` | `examples/api/README.md` | The `examples/sdk/01-<scenario>.md` and `examples/api/01-<entry>.md` files are deliberately not auto-generated — they describe **specific behavior** of the user's library, which this skill does not know. The `examples/{sdk,api}/README.md` files include a "How to ad

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.