agentsclimarketplace

Nd environment scaffold

Skill jpoindexter/nd-skills/skills/nd-environment-scaffold

Diagnosis-free neurodivergent support skills for AI coding agents, with executive-function scaffolds and always-on Claude/Codex behaviors.

Install
npx -y skills add jpoindexter/nd-skills --skill nd-environment-scaffold

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 23 days oldThe repository was created 23 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Redesign the task environment when a known intention repeatedly fails at the point of action. Use when reminders arrive too early or late, tools or state are hard to find, choices or steps create friction, a system depends on memory, or repeated failure shows that effort alone is not enough.

SKILL.md

2.4 KB, as published. Nobody here has run it

Environment Scaffold

Make the intended action easier to see, start, continue, and resume. Change the environment before demanding more willpower.

Procedure

  1. Name the intended action and its point of performance: the exact place and moment where it must happen.
  2. Audit friction at that point:
    • Is the cue visible when action is possible?
    • Are required tools, files, permissions, and state already available?
    • Are there too many decisions or steps?
    • Does the system rely on remembering something out of sight?
    • Is support available at the difficulty level that actually occurs?
  3. Add the smallest fitting scaffold:
    • structure: a default, template, container, launch point, or fixed sequence
    • support: a checkpoint, body-double surface, automation, or named helper
    • strategy: a concrete method tailored to the observed barrier
  4. Put the cue and required state at the point of performance.
  5. Test the scaffold in the real workflow.
  6. Keep it only if it reduces total effort, including maintenance.

Prefer one visible home for state over duplicate systems. Prefer recognition over recall, defaults over repeated decisions, and an exact re-entry action over a general reminder.

Support Levels

  • self-support: one cue, checklist, or default
  • collaborative support: a shared checkpoint or working surface
  • specialist support: qualified human help when safety or domain expertise requires it

Fade scaffolding when it stops reducing friction. Do not make the user maintain a support system for its own sake.

Guardrails

Do not encode diagnoses, inferred traits, or private biography into task state. Do not add surveillance, coercive reminders, artificial urgency, or a more elaborate system than the task warrants. Preserve user control and easy override.

Source Basis

Synthesize Kolberg and Nadeau's structure-support-strategy framework, visibility and launch-point techniques; Dawson and Guare's task and environment modifications at the point of performance; and NESTL's proactive, flexible, diagnosis-free adjustments.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.