agentleFS
Sign inStart free
LangChainKnown publisherlangchain-ai/design-agent/.agents/skills/design-agent-update/SKILL.md

design-agent-update

Skill2 starsChanged 14 days agoApache-2.0View on GitHub

Bring a fork or clone of Design Agent up to date with the upstream repository while keeping the team's brand, skills and edits, rebuild what changed, and redeploy safely. Use when someone asks to update, upgrade or pull the latest Design Agent.

  • Reads credentials

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add the remote once: git remote add upstream https://github.com/langchain-ai/design-agent.git.

    line 12
  2. Very specific:

    If sandbox/setup.sh changed: uv run design-agent sandbox build && uv run design-agent sandbox test.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Update from upstream

The brand pack (workspace/brand/), licensed fonts (private-fonts/) and .env are Git-ignored, so an update never touches them. The team's own skills and instruction edits can conflict.

  1. git status. Commit the person's local work first, or ask; never use a bare git stash.
  2. Add the remote once: git remote add upstream https://github.com/langchain-ai/design-agent.git. Then git fetch upstream and read the new entries in CHANGELOG.md for breaking changes.
  3. Merge upstream/main into the person's branch. In conflicts, keep their skills and instruction edits and take upstream's code; ask when a conflict touches both.
  4. uv sync, uv run design-agent doctor, uv run pytest -q, uv run design-agent skills verify.
  5. If sandbox/setup.sh changed: uv run design-agent sandbox build && uv run design-agent sandbox test; for Managed Deep Agents, also uv run design-agent sandbox publish (the snapshot name follows the recipe's hash).
  6. Try the update on a test copy (uv run mda deploy --name design-agent-test), then deploy the team's agent after a yes (design-agent-deploy).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free