randommonicle
- 46 skills
- 0 followers
- 7 hours ago last updated
- ▌ Handover · randommonicleProduce a structured handover note when the context window fills or the user asks to wrap up. Run /context first to read the real percentage; never estimate — and where the harness cannot invoke /context, record the gap verbatim rather than inventing a figure. Triggers when the context band reaches amber or red, when the user says "wrap up", "handover", or "hand off", or before deliberately ending a long working session.
- ▌ Unslop UI · randommonicle bundleStrips the cues that make a website read as AI-generated and forces a deliberate, project-specific design choice instead of the model's default. It does not impose a look or hand you taste. It removes tells (default shadcn/Tailwind, AI-purple gradients, gradient heading text, unprompted neon glow, emoji-as-icons, the centered hero plus three feature cards) AND the newer cream-plus-serif-plus-sage "tasteful default" that trading one default for another creates. Grounded in a 47-subreddit, 3.2M-post Reddit analysis of what people flag as AI slop. Use whenever building, styling, reviewing, refactoring, or auditing any website, landing page, web app UI, dashboard, or front-end component, especially when the user wants a site to look custom or human rather than AI-generated, or mentions AI slop, looks AI-made, generic, vibe-coded, Tailwind, or shadcn. Trigger even if they never say vibe-coded.
- ▌ Plan First · randommonicleState the file list, test list, and out-of-scope items before writing code on any non-trivial commit. Triggers on requests to implement a feature, add a schema-touching change, build a new module, or perform a multi-file refactor. Skip on trivial one-line fixes and doc typo corrections.
- ▌ Safe Smokes · randommonicleNever run destructive operations against shared or live data in tests, smokes, or seeds. Flip-and-restore with try/finally instead of delete; seed in beforeAll and tear down in afterAll; restore shared state exactly as found. Triggers when writing or editing any test, smoke, or seed script that connects to a shared or live database, Supabase or otherwise. Does not trigger on tests that run only against mocks, fixtures, or an in-memory database.
- ▌ Unslop Text · randommonicle bundleStrips the cues that make prose read as AI-generated and forces a deliberate human voice instead of the model's default register. It has no house style and does not write for you. It removes the cited tells (the em dash, the "it's not just X, it's Y" cadence, assistant boilerplate, the delve/tapestry diction, listicle scaffolding, the "in conclusion" wrap-up) and warns against the over-corrected "trying not to sound like AI" register that swaps one default for another. Grounded in a Reddit analysis of 89,239 posts (7,984 on-topic) across roughly 50 AI, writing, and SaaS subreddits of what people name as a giveaway. Use when writing, drafting, editing, rewriting, reviewing, or auditing any prose for a reader (a post, email, essay, README, or marketing copy), and especially when the user wants it to sound human rather than AI, or says it "sounds like ChatGPT," "reads like AI," "is too polished," "de-slop this," or "make it sound like me." Trigger even if they never say "AI tell."
- ▌ One Real Ride · randommonicleBefore declaring any deployed or user-facing change done, shipped, or closed out, run one real end-to-end invocation through the real seams — the deployed function, a real login and JWT, the real model call, the real browser or device. Green CI, green smokes, and a clean typecheck prove the layers; only the ride proves the seams. Triggers on "done", "shipped", "live", closing out a feature, and after any migration that existing code reads. Does not fire mid-implementation on individual command results (verify-the-effect's norm covers per-signal checks), nor on changes with no deployed or user-facing surface.
- ▌ Checkpoint Log · randommonicleKeep a live, committed checkpoint log during any work unit expected to span multiple commits or sessions. Each commit ships with a short note in the log, what the commit did, the key decision and why, any deviation from plan; closing the unit requires an explicit walk of the checklist including the wiring steps. Triggers when starting multi-commit work, when resuming a unit after a crash or a gap, and when declaring a multi-commit work unit done. Does not fire on single-commit fixes, where the commit message carries the note.
- ▌ Context Economy · randommonicle bundleKeep the context window small and its prefix stable, because every token in it is re-sent on every later turn. Read slices instead of whole files, cap tool and log output before it lands, isolate high-volume work behind a summary, and clear rather than compact between unrelated tasks. Triggers when about to read a large file, log, dataset, transcript or search result into context; when a session has grown long, auto-compacted, or hit a usage limit mid-task; when writing or growing an instruction file (CLAUDE.md, AGENTS.md, GEMINI.md) or a skill; and when assembling a prompt from a static part and a varying part. Does not fire on pricing a recurring job or reporting what an action cost (price-the-spend), shaping a multi-agent roster (commission-the-roster), writing the handover at the end of a session (handover), or designing a product path that sends data to a model (ai-surface-discipline).
- ▌ Earn Every Line · randommonicleNothing enters a file without a present need. Code earns its place by a caller that exists, a comment by saying what the code cannot, flexibility by a stated requirement. Triggers on over-engineered, over-commented, YAGNI, speculative, gold-plating, "just in case", "future-proofing", "flexibility", and on "simplify" / "keep it simple" (both over-correction ditches are fenced); more generally when writing or refactoring code. Does not fire on recognising AI-written code (unslop-code owns the audit), failure-message wording (honest-failure-surfacing), or client-supplied data rules (server-side-authority).
- ▌ Mass Red Triage · randommonicleWhen a test suite goes from green to broadly red, classify before debugging. Find the first root failure (cascades multiply one fault), check for rate-limit walls, truncated runs, and environment defects, and bound the change's blast radius via the lockfile and diff before attributing blame. Triggers whenever a suite or CI run turns broadly red, or a run's failure count looks implausible in either direction. Does not fire on a single failing test or on suites already red for known, recorded reasons.
- ▌ Price The Spend · randommoniclePrice anything that recurs BEFORE it ships, and report what an action actually cost AFTER it runs. Triggers when adding or reviewing a cron job, scheduled workflow, nightly build, keep-warm ping, polling loop, always-on container, log retention or storage growth, a paid tier or subscription upgrade, or a runner or instance size; and after any subagent batch, agent workflow, LLM API call, or one-off cloud job. Also when a metered allowance, spending limit, or quota is exhausted. Does not fire on capping or rate-limiting an endpoint, which is guard-the-spend-paths.
- ▌
- ▌ Live State First · randommoniclePlaybook for the always-on norm "probe live state before building from any described state". Load when about to write code, SQL, config, or a fixture from a handover, memory note, README, audit tracker, or code comment, or when two documents disagree. Does not fire on repo/PR/branch state (parallel-work-recon owns repo probes) or on state you observed yourself this session.
- ▌ Trace One Record · randommonicleBefore combining two figures into a derived total, or asserting that one set of amounts sits outside another, trace a single record end to end through both sources to establish what each actually contains. Triggers on any total owed, due, outstanding, exposed or net; on adding, subtracting or netting figures from different reports, systems or dates; on the phrases "sits outside", "excludes", "in addition to", "the two therefore add"; and on any reconciliation between two sources. Does not fire on arithmetic within a single report, on a figure quoted from one source with no combination, or on citations of files and commits in prose, which belong to verified-citations.
- ▌ Blast Radius Grep · randommonicleThe unit of change is the action or the fact, never the named list of places someone handed you. Before shipping a gate, constraint, rename, drop, or a correction to any duplicated, mirrored, or denormalised value, grep the whole repo — app, tests, seeds, scripts, open branches, and the built or rendered output — and fix every occurrence in the same pass; back a value copied into a second store with a trigger and a zero-rows drift-check query. Triggers on "change X in A and B" instructions, constraint or gate additions, drops and renames, denormalising a value, correcting any fact that is not single-sourced, and concluding anything from a sweep whose run errored or whose output was truncated. Does not fire on checking references in prose documents — verified-citations owns citation accuracy; this skill owns content duplication.
- ▌
- ▌ Prove It Can Fail · randommonicleEvery test, seed, verification script, CI gate, or check must demonstrably be able to fail when the thing it guards is broken. Ask of each check "what does this print if the thing is broken?" Triggers when writing or reviewing any test, smoke, seed, verification file, or CI job, when marking a test skipped, and when arming a new gate. Does not fire on triaging an already-red suite (mass-red-triage) or on how tests touch shared data (safe-smokes).
- ▌ Secrets In Output · randommonicleNothing that can carry a secret value may reach a tool result, because the transcript is a synced file re-sent on every turn. Check an env var by presence and length only, list names not values, read a .env file by its keys, capture provider status output and API responses into a variable and print a named allowlist, and dry-run the output shape on a dummy value first. Triggers on any command, script or API call that names an env var, a .env file, a key, token, password or secret, or a credential-carrying header. Does not fire on whether a changed value is live (env-change-verification) or on comparing a secret (constant-time-secret-compare).
- ▌ Verify The Effect · randommoniclePlaybook for the always-on norm "never report success from a proxy signal — assert the actual effect or artifact". Load when a status signal (green CI step, HTTP 200, "accepted", exit 0, progress bar) is about to be read as success, when a step's entire output is a side effect, or when routed here from the one-real-ride done gate. Does not fire on test-suite results (prove-it-can-fail) or on declaring a whole feature done (one-real-ride owns that moment).
- ▌ Cross Agent Review · randommonicle bundleAdversarially review a specific change, design, or finding by having Claude debate one or more INDEPENDENT AI agents (Gemini via the agy CLI or GPT via the codex CLI, driven by Claude with no pasting; or a chat the user drives; several seats at once) over a shared file relay, with mandatory file:line citations, live read-only evidence, and a converge-or-two-positions outcome. Use when the user wants a different model's adversarial take before acting, mentions Antigravity / cross-agent / agent-exchange / "hash it out with Gemini", or wants a finding stress-tested by independent models. NOT for whole-project audits (that is committee-review) or quick single-pass checks. Needs at least one second agent, driven headlessly through the CLI transport or by the user in a chat, and a shared directory both sides can read and write.
- ▌ Verified Citations · randommonicle bundleStops fabricated and drifted references in any document that cites code, schema, config or history. Load BEFORE writing or reviewing a handover, design doc, plan, spec, decision log, lessons entry, audit, review report, PR description, or commit message that points at files, line numbers, migrations, commits, PRs or dates. The failure it prevents is specific and measured, a model grounds technical facts correctly while inventing the PATH around a borrowed line number, drifting a line number onto a blank line, citing a range that spans unrelated blocks, or misattributing when something landed, and then self-reports that everything was verified. Triggers on file:line, "landed in PR", "added on", "see some/file.ts", migration numbers, or any claim a reader would act on without re-deriving. Do not load for writing code itself.
- ▌ Confirm Before Push · randommonicleAlways ask explicitly before pushing to a remote or fast-forwarding a protected branch. Per-action authorisation, not standing approval. Triggers on any git push, merge, or branch fast-forward operation, regardless of whether previous pushes in the same session were approved.
- ▌ Date Parse Utc Safe · randommonicleIn a UTC server or serverless runtime, new Date("YYYY-MM-DD") is UTC midnight and renders as the previous day in western timezones. Parse date-only strings into explicit local components (new Date(y, m-1, d)) anywhere a date becomes a display string or a day-of-week. Triggers when parsing a date-only string server-side or computing a printed day from one. Does not fire on full ISO timestamps carrying explicit timezones.
- ▌ Flag Deferred Items · randommonicleWhen proposing anything as deferred, out of scope, or "for a later phase", plant a grep-able flag at the place where the deferred work will land. Triggers whenever the words "deferred", "out of scope", "later commit", "later phase", "future work", or similar appear in plans, commits, or design discussions.
- ▌ No Silent Data Drop · randommoniclePlaybook for the always-on norm "filters and gates hide empty things; they never drop content". Load when adding any filter, gate, continue, catch, or fallback to a rendering or export path, when parsing model output that carries content, or when two renderers must produce the same content. Does not fire on error-message wording or telemetry levels (honest-failure-surfacing) or on filters over data the user never receives.
- ▌
- ▌ Rerun Before Verdict · randommonicleNo verdict from a single uncontrolled run. A fix is proven by re-running the case that failed; a component's deadness or value is proven by a with/without comparison on the current system; a surprisingly good result stays a candidate until three consistent datapoints or a controlled before/after diff back it. Triggers when about to declare a fix proven, code dead, a component worthless, an approach impossible, or a result a breakthrough. Does not fire on interpreting a single success signal (verify-the-effect), on check integrity (prove-it-can-fail), or on the epistemic status of second-hand claims (findings-are-evidence).
- ▌
- ▌ Commission The Roster · randommonicleBefore spawning a fleet of agents, publish a roster for the operator's approval - role, model tier, token budget, scope and single artifact per agent - and brief each agent with pre-verified facts instead of questions. Triggers when appointing a lead agent, delegating a multi-agent wave, planning a commission whose shape is not yet known, choosing which model tier does which job, or when a usage window emptied faster than the work justified. Does not fire on spawning one agent for one bounded task, and does not price the result (price-the-spend reports the burn afterwards).
- ▌
- ▌ Findings Are Evidence · randommonicleA subagent, reviewer, or scout report is evidence, not findings — and so is your own first-hand defect analysis. Re-derive every Critical or High claim, everything touching a regulatory anchor, and the reasoning about the fix from the primary source before acting or writing it into a durable artifact. Triggers when consuming any agent or reviewer output and when recording a defect or fix analysis. Does not fire on low-severity suggestions with no gating or regulatory consequence — sample those rather than re-deriving them all.
- ▌ Guard The Spend Paths · randommonicleWhen creating or reviewing any endpoint or control that touches money or shared state, two rules apply together. Every endpoint that spends money (LLM, email, SMS, payment) or writes shared state (bookings, slots) gets a per-IP volume cap the day it is created — anyone can POST directly, bypassing the UI. And any guardrail on that path written to fail open (origin allowlist defaulting to permit, auth that skips on a missing header) is inert until explicitly closed, and its failure is silent — name the real primary defence. Does not fire on internal-only endpoints behind service-role auth with no paid upstream; internal fan-out caps belong to lock-at-the-chokepoint.
- ▌ Server Side Authority · randommonicleFour server-side authority rules for any client-facing backend. Never trust a client-supplied storage path or object id — derive it server-side from the row the caller owns. An RLS self-update policy must scope columns, not just rows, or a user can promote their own role. Every exposed table gets RLS enabled or its grants revoked — a code comment is not a control. Escape all dynamic output in admin surfaces. Triggers when adding or reviewing a route that accepts client-supplied paths/ids, an RLS self-update policy, a new public-schema table, or an admin dashboard render. Does not fire on general security review (the security-review command) or client-side validation UX.
- ▌ Skill Library Builder · randommonicle bundleTurn a real repository into a project-specific skill library that preserves a senior engineer's operating knowledge, so juniors and smaller models can carry the project forward. Load when asked to build, refresh, or audit a skill library or engineering playbook for a codebase, to capture tribal knowledge before someone leaves, to onboard engineers, or to make a repo easier for AI agents to work on. This is project-agnostic and installed user-level, so it applies to every project on this machine; the PropOS repo's own propos-* family is the worked example it was derived from. Do not load it to write a single skill on a topic you already know (write that skill directly).
- ▌ Lock At The Chokepoint · randommonicleSerialise shared operations at the single module-level chokepoint every caller passes through, never in per-instance state — and cap fan-out there too. A check-then-act idempotency guard protects sequential retries but loses the race under concurrency. Triggers when adding a lock, in-flight guard, dedupe check, or rate cap where multiple callers, component instances, or loops can invoke the same shared operation, and when writing any internal retry or resume loop over a batch. Does not fire on recording the status of an external send — outbound-side-effect-idempotency owns send-then-record.
- ▌ Env Change Verification · randommonicleAn environment variable change is not live until the artifact that reads it is rebuilt, redeployed, or re-reads it — and a wrong-but-present value fails silently. Know for each variable whether it is baked at build time or read at request time. Triggers when adding or editing any env var, CI secret, or hosted config value, and when a CI or cloud build consumes build-time env. Does not fire on database schema changes (db-migration-verification) or on code-only changes with no config surface.
- ▌ Working Lean · randommonicleGets faster, more accurate answers by keeping each conversation to one matter and sending the material that bears on it without the material that does not. Use when someone is about to attach a mailbox or file export, a whole drive or client folder, or many documents at once; when a conversation has run long, drifted across unrelated matters, or started repeating itself, losing detail or contradicting something said earlier; when someone has reached or is approaching a usage limit, or asks how to make their allowance last; and when choosing which folder to point a Cowork task at. Covers what to attach and what to leave out, why completeness beats economy on a lease or a set of accounts, and when to start a fresh conversation instead of continuing.
- ▌ Honest Failure Surfacing · randommoniclePlaybook for the always-on norm "one message per failure mode; error level is for terminal states only". Load when writing a catch block, a user-facing error string, a disabled control, a progress indicator, or choosing telemetry levels. Does not fire on content loss through filters (no-silent-data-drop) or on test skip semantics (prove-it-can-fail).
- ▌ Reproduce The Real Build · randommonicleBefore pushing anything a CI or release pipeline will compile, run the exact production build command locally — the test runner tolerates syntax and dependency drift the release build rejects. Prove any toolchain fix by reconstructing from tracked manifests alone (npm ci into a clean directory). Triggers before pushing build-config, lockfile, or toolchain changes, and when tests pass but deployment builds fail. Does not fire on test-only changes no release pipeline compiles.
- ▌ DB Migration Verification · randommonicleEvery database migration plan ships with a post-apply verification query that reads catalog state directly, separate from any runtime tests. Triggers on any work involving a database migration, schema change, RLS policy change, trigger change, or constraint change.
- ▌ Email Delivery Verification · randommonicleA 2xx from a transactional email API means accepted, not delivered. Verify actual delivery in the provider's dashboard or webhooks, check the account-level suppression list, verify every recipient leg of a multi-recipient flow, and confirm a mailbox exists before pointing a send at it. Triggers when adding or changing any transactional email send or recipient address, and when diagnosing "the email never arrived". The provider-specific child of verify-the-effect. Does not fire on non-email side effects (outbound-side-effect-idempotency) or on the content of the email.
- ▌ Enforce Invariants In Build · randommonicleA rule asserted only in prose — "single source of truth", "never auto-X", "these must match" — is a comment, not a control; if a violation can exist without failing the build, one eventually will and it will look official. Triggers when writing or encountering any comment, doc, or convention that asserts an invariant nothing enforces. Does not fire on deferral markers (flag-deferred-items) or on rules already carried by a test, constraint, or trigger.
- ▌ Substantiate Outward Claims · randommonicleAny certification, award, statistic, or third-party performance claim shown to a customer needs a primary or independent source, or explicit attribution ("the manufacturer states…") — never asserted as fact, and never trusted from an AI summary, which blends marketing with real product names. Triggers when writing customer-facing copy, marketing pages, or an assistant's knowledge base entries that assert such claims. Does not fire on internal docs citing code or history — verified-citations owns those.
- ▌ Constant Time Secret Compare · randommonicleCompare bearer tokens, API secrets, signatures, and password-equivalents with a constant-time comparison (hash both sides, then crypto.timingSafeEqual) — never == or short-circuiting string equality. Triggers when writing any code that checks a secret against a stored or expected value. Does not fire on comparing non-secret identifiers.
- ▌
- ▌ Outbound Side Effect Idempotency · randommonicleCode that performs an external side effect (email, SMS, payment, webhook) and then records its status must choose which failure harms the recipient less — lost or duplicated — and design for that. A read-then-write "already sent?" check is not a lock. Triggers when writing any send-then-record path or adding retry logic around an external send. Does not fire on internal batch retry loops with no external recipient — lock-at-the-chokepoint owns those.