AtomiCloud
@AtomiCloud Organization
Public Skills
writing-resolver-javascript
by AtomiCloud
Write or modify CyanPrint resolver code in JavaScript. Use when the user asks to change conflict resolution logic, modify merge strategies, handle file origins, or change resolution behavior. Covers entry point (StartResolverWithLambda), ResolverInput/ResolverOutput, ResolvedFile, and FileOrigin. Must ensure commutativity and associativity (sort, unique, deterministic ordering).
testing-template
by AtomiCloud
Test this CyanPrint template. Use when the user asks to write tests, add test cases, update snapshots, or debug template test failures. Covers test.cyan.yaml format with answer_state, deterministic_state, validate commands, and expected output.
documenting-template
by AtomiCloud
Document this CyanPrint template into README.MD. Use when the user asks to document the template, write a README, explain how to use the template, or add usage documentation. Reads cyan.yaml and entry point code to generate accurate, artifact-specific docs.
testing-resolver
by AtomiCloud
Test this CyanPrint resolver. Use when the user asks to write resolver tests, add test cases with conflicting files, update snapshots, or debug resolver test failures. Covers test.cyan.yaml format with resolver_inputs (directory paths with origin), config, and expected output.
taskfile-conventions
by AtomiCloud
Taskfile conventions. Use when creating or modifying Taskfile.yaml or tasks/.
ci-cd-workflows
by AtomiCloud
CI/CD workflow patterns. Use when creating or modifying GitHub Actions workflows.
semantic-release
by AtomiCloud
Semantic release configuration and workflow. Use when configuring releases or understanding versioning.
conventional-commits
by AtomiCloud
Conventional commit conventions. Use when writing commit messages.
docker-push
by AtomiCloud
Docker image build and push to container registry. Use when adding or modifying Docker image builds and pushes to GHCR.
shell-conventions
by AtomiCloud
Shell script conventions. Use when writing or modifying shell scripts in scripts/.
linting
by AtomiCloud
Linting conventions. Use when running or configuring linting.
service-tree
by AtomiCloud
Service Tree (LPSM) naming conventions. Use when naming resources, labels, tags, or when terms like LPSM, landscape, platform, service, module appear.
upgrade
by AtomiCloud
Upgrade all CyanPrint SDK packages and Docker runtime versions across templates, plugins, and processors (TypeScript, JavaScript, Python, .NET), then run tests to validate. Use when upgrading dependencies, updating SDK versions, refreshing packages, updating Docker images, or running /upgrade.
nix
by AtomiCloud
Use for ALL Nix flake configuration questions. This includes file structure (flake.nix, nix/, .envrc), adding/removing packages or binaries, PATH configuration, development shells, pre-commit hooks, formatters, linters, enforcers, environment variables, adding registries, and how the Nix template structure works. Use when user asks about nix, flake, packages, binaries, shells, PATH, formatting, linting, git hooks, or registries.