Instructions file CodexOpenCode
Instructions for arch3rPro/1Panel-Appstore, covering repository guidelines, project shape, app package layout, 1panel conventions and app creation workflow.
Instructions file CodexOpenCode
Instructions for arch3rPro/1Panel-Appstore, covering repository guidelines, project shape, app package layout, 1panel conventions and app creation workflow.
Skill Claude CodeCodex
Use when packaging Docker deployments as 1Panel local app store apps, including GitHub projects, docker-compose.yml files, docker run commands, app metadata, version directories, icons, README files, and 1Panel validation.
Plugin Claude Code
Generalized, project-agnostic development-specification skills, as an installable Claude Code plugin.
Plugin Claude Code
dsh-skills — generalized development-specification skills (defensive patterns, code conventions, testing tiers, prose standards, decision records, review/process discipline), extracted from DeepSeek Harness conventions and shaped by the mattpocock/skills architecture.
Instructions file CodexOpenCode
Instructions for arch3rPro/dsh-skills, a project described as: Generalized development-specification skills distilled from DeepSeek Harness's engineering conventions — defensive patterns, code conventions, testing tiers, prose standards, decision records, review and PR discipline.
Instructions file
Instructions for arch3rPro/dsh-skills, covering claude.md — dsh-skills, repository layout, standing orders and editing these instructions.
Skill Claude CodeCodex
General code conventions that keep a codebase predictable — reversible side effects, switching on discriminant tags, explicit-over-implicit at boundaries, configuration over hardcoded tunables, branded opaque ids, trusting types at typed boundaries, and honest empty catches. Use when writing, reviewing, or refactoring…
Skill Claude CodeCodex
Defensive-programming patterns to apply when writing or reviewing lifecycle, concurrency, subprocess, teardown, error-reporting, or untrusted-IO code. Use when a change touches async setup or teardown, callbacks, spawned processes, workers, event listeners, disposal, error aggregation, temp files, or anything…
Skill Claude CodeCodex
Design for swappable capabilities — when a capability may have multiple implementations or consumers, separate it into contract / implementation / consumer so they vary independently, and route new behavior through documented extension points instead of patching a core. Use when designing a new capability, deciding…
Skill Claude CodeCodex
Know and enforce your module dependency graph — derive inter-module edges from the canonical dependency signal, catch circular dependencies, and enforce intended layering with tooling. Use when a codebase has many modules or packages and layering is a real concern.
Skill Claude CodeCodex
Decide where documentation belongs so each fact has exactly one home — classify documents as tutorial or reference, place each fact in the tier that owns it and link everywhere else, and keep budgets as guardrails rather than reduction targets. Use when writing, moving, restructuring, or auditing documentation, or…
Skill Claude CodeCodex
Maintain an explicit matrix of which module dispatches each event and which modules listen — many-to-many, with deliberate bypass sites noted — so event contracts stay a single source of truth. Use in event-driven or pub/sub systems where events cross module boundaries.
Skill Claude CodeCodex
Write prose that preserves every contract while deleting reasoning transcripts, repetition, and decoration — across comments, JSDoc, docs, prompts, diagnostics, and user-visible strings. Use when writing, reviewing, trimming, restoring, or auditing prose, or deciding where documentation or a comment is required. It…
Skill Claude CodeCodex
Review a change along two axes — Standards (does the code follow the repo's documented standards, plus a smell baseline?) and Spec (does it faithfully implement the originating issue/spec?) — run as parallel sub-agents and reported side by side, prioritizing correctness, lifecycle, and security over style. Use when…
Skill Claude CodeCodex
Record design decisions as Architecture Decision Records (ADRs) so the why survives — with a classification, a lifecycle, and a mandatory alternatives-considered section. Use when making or proposing a non-trivial design decision, when reviewing a change that affects architecture, contracts, processes, or formats, or…
Skill Claude CodeCodex
Run the smallest set of checks that covers an outgoing change before pushing, committing, or claiming checks pass — select evidence by the surface the diff touches, never reflexively run the full suite, and fix or explain a failure rather than pushing and hoping CI differs. Use before push, force-push, marking ready…
Skill Claude CodeCodex
Write a backward-looking failure record — executive summary, timeline, root cause, and guardrails — when a bug was subtle, systemic, and costly to rediscover. Use after a hard incident or regression, or when deciding whether one is owed. It records what broke and why it escaped; complement it with decision-records…
Skill Claude CodeCodex
Keep pull-request history deliberate and safe — split independent changes, rewrite with lease-protected force-push (never raw force), apply one kind label plus all material area labels, and land a stack of dependent PRs through the platform's native stack feature rather than manually merging and retargeting. Use when…
Skill Claude CodeCodex
Respond to code review across a dependent PR stack — fix on the PR that introduced the issue, propagate the fix up-stack, keep each review fix a distinct commit, lease-protect any rewrite, and re-audit threads, approvals, and checks after every rewrite. Use when review comments span several stacked PRs.
Skill Claude CodeCodex
Assert only authoritative state at runtime — authoritative event streams or mutable data, never service or method presence — with each check owned by the module it guards and failing loud at startup. Use when adding runtime invariant checks, or deciding what an invariant may assert. It complements testing-tiers, which…
Skill Claude CodeCodex
Choose the right test tier for a change and keep the suite meaningful — unit, integration, real-entry-path, end-to-end, and snapshot tiers; test the real entry path rather than a hand-built harness; verify the world rather than the component's self-report; prefer the real implementation over a mock; and treat line…
Plugin Claude Code
Reusable agent skills, roles, and workflows for ArkSpace orchestration.
Plugin Claude Code
ArkSpace is a creative workspace for orchestrating reusable agent skills, roles, and workflows.
Instructions file CodexOpenCode
Instructions for arch3rPro/ark-space, covering agent guidance, project contract, default workflow, validation and source governance.