Run any Skill in Manus with one click

environmental-preparations

Stars0

Forks0

UpdatedJune 25, 2026 at 23:36

Running log of the user's environment preferences and configuration changes — CLAUDE.md rules, settings, and conventions. Use to recall how the user likes their environment set up, and append a dated entry whenever you make an environment change (anything that isn't building a skill).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

CrAzyScreamx

CrAzyScreamx/calude-marketplace

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	environmental-preparations
description	Running log of the user's environment preferences and configuration changes — CLAUDE.md rules, settings, and conventions. Use to recall how the user likes their environment set up, and append a dated entry whenever you make an environment change (anything that isn't building a skill).

Purpose

Claude has no memory across sessions. This skill is the durable record of how the user likes the environment configured. Read it when preparing a project's environment; append to it whenever an environment change is made (CLAUDE.md edits, settings, conventions — anything that isn't a skill build).

How to log

Append a new entry under Change log, newest first: a dated heading, what changed, and where it applies.

Change log

2026-06-22 — LLM token/cost discipline as a standing CLAUDE.md rule

What: Added an "LLM token/cost discipline" rule to global ~/.claude/CLAUDE.md: terse instructions, StructuredOutput over inline schemas, TOON over JSON for payloads, drop empty/no-finding sections, target <15k input tokens — applied when first writing any LLM agent prompt.
Where: C:\Users\Amit\.claude\CLAUDE.md (Working conventions section).
Why: Cost minimization (~$0.2/run, "instructions too long") is a standing constraint for the user, but every new agent/prompt was built verbose and then re-trimmed on request. The rule makes prompts born lean.

2026-06-22 — Standing conventions into global CLAUDE.md (fix skill auto-trigger friction)

What: Added a "Working conventions (apply unconditionally)" section to the global ~/.claude/CLAUDE.md: (1) the plan.md/tasks.md planning workflow, and (2) always follow python-guidelines before writing Python.
Where: C:\Users\Amit\.claude\CLAUDE.md.
Why: Skills don't always auto-fire, so the user kept re-asking "did you use the skill?" and re-explaining the same conventions each session. CLAUDE.md rules apply unconditionally on every machine that syncs it, so the two most-repeated conventions no longer depend on skill triggering. The project-planning and python-guidelines skill descriptions are already trigger-tuned; the global rules are the durable backstop.

2026-06-22 — Project planning convention as a project-root CLAUDE.md rule

What: Added a "Project planning" snippet to drop into each project's root CLAUDE.md, declaring plan.md as the source of truth and tasks.md as the derived execution breakdown (Milestones, sub-tasks, status table), and instructing session-start to resume at the next Pending/In Progress task.
Where: The snippet lives in the project-planning skill ("Project-root CLAUDE.md rule" section), which offers to add it to a project root on first setup.
Why: The user re-explained this start-of-project ritual nearly every session; encoding it removes the need to re-describe it.

More from this repository

same repository

feature-interviewer

CrAzyScreamx/calude-marketplace

Gathers the project details each specialized coder needs before it writes code — frontend theme/typography/layout, backend API/caching/DB shape, containerization build/runtime shape, CI/CD pipeline shape — then hands each coder only its scoped answers. Use before invoking any coder, once a worktree feature is scoped, or whenever splitting work across parallel coders.

2026-07-100

guideline-builder

CrAzyScreamx/calude-marketplace

Builds a missing `<lang>-guidelines` skill for a language/stack, packaged as a standalone plugin and registered in a marketplace, before any code is written. Use whenever no `<lang>-guidelines` skill exists yet for the stack about to be coded (React, FastAPI, Docker, CI/CD, or anything else) — invoke this FIRST, before any coder runs, then follow the generated skill.

2026-07-100

containerization-guidelines

CrAzyScreamx/calude-marketplace

Invoke BEFORE writing any Dockerfile or containerizing an app for deployment. Language-agnostic image-build conventions — multi-stage builds, non-root, layer caching, healthcheck, and hadolint tooling.

2026-07-070

python-guidelines

CrAzyScreamx/calude-marketplace

Invoke BEFORE writing any Python code (CLI tools, libraries, APIs, modules, tests). Encodes the project's Python + uv + ruff + pyright + pytest architecture, plus conditional references for DB, API, and caching work.

2026-07-070

react-guidelines

CrAzyScreamx/calude-marketplace

Invoke BEFORE writing any React/TypeScript frontend code (components, hooks, routes, forms). Encodes the project's React + TypeScript + Vite + pnpm conventions, architecture rules, and tooling commands.

2026-07-070

project-planning

CrAzyScreamx/calude-marketplace

Read a project's plan.md and build or update a tasks.md broken into Milestones and sub-tasks, with per-task descriptions and a status tracking table, splitting tasks that are too large and marking progress. Use at the start of a project or session ("read the plan", "build a tasks file", "continue where we left off"), whenever a plan.md exists and tasks need to be derived or refreshed, or when the user asks to track/update project progress.

2026-06-250

name	environmental-preparations
description	Running log of the user's environment preferences and configuration changes — CLAUDE.md rules, settings, and conventions. Use to recall how the user likes their environment set up, and append a dated entry whenever you make an environment change (anything that isn't building a skill).

Purpose

How to log

Append a new entry under Change log, newest first: a dated heading, what changed, and where it applies.

Change log

2026-06-22 — LLM token/cost discipline as a standing CLAUDE.md rule

What: Added an "LLM token/cost discipline" rule to global ~/.claude/CLAUDE.md: terse instructions, StructuredOutput over inline schemas, TOON over JSON for payloads, drop empty/no-finding sections, target <15k input tokens — applied when first writing any LLM agent prompt.
Where: C:\Users\Amit\.claude\CLAUDE.md (Working conventions section).
Why: Cost minimization (~$0.2/run, "instructions too long") is a standing constraint for the user, but every new agent/prompt was built verbose and then re-trimmed on request. The rule makes prompts born lean.

2026-06-22 — Standing conventions into global CLAUDE.md (fix skill auto-trigger friction)

What: Added a "Working conventions (apply unconditionally)" section to the global ~/.claude/CLAUDE.md: (1) the plan.md/tasks.md planning workflow, and (2) always follow python-guidelines before writing Python.
Where: C:\Users\Amit\.claude\CLAUDE.md.
Why: Skills don't always auto-fire, so the user kept re-asking "did you use the skill?" and re-explaining the same conventions each session. CLAUDE.md rules apply unconditionally on every machine that syncs it, so the two most-repeated conventions no longer depend on skill triggering. The project-planning and python-guidelines skill descriptions are already trigger-tuned; the global rules are the durable backstop.

2026-06-22 — Project planning convention as a project-root CLAUDE.md rule

What: Added a "Project planning" snippet to drop into each project's root CLAUDE.md, declaring plan.md as the source of truth and tasks.md as the derived execution breakdown (Milestones, sub-tasks, status table), and instructing session-start to resume at the next Pending/In Progress task.
Where: The snippet lives in the project-planning skill ("Project-root CLAUDE.md rule" section), which offers to add it to a project root on first setup.
Why: The user re-explained this start-of-project ritual nearly every session; encoding it removes the need to re-describe it.