Claude Code

Install

curl -fsSL https://claude.ai/install.sh | bash

This is third-party code. Review the repository files before installing.

What it does

Claude Code runs in the terminal, understands the project and performs routine tasks from natural-language requests: writing and editing code, explaining complex parts and handling git workflows. It can be used in an IDE or invoked by tagging @claude on GitHub. The repository contains official plugins with commands, agents and skills such as frontend-design, code-review and plugin-dev.

Who it is for. Developers who want to delegate tasks in a real repository to an agent.

Example request

Find why tests in the payments module fail, fix them and commit with a clear message

Limitations

Installing via npm is deprecated; the native installer, Homebrew or WinGet are recommended. Claude Code collects usage data and feedback, as described in the data usage policy.

How to disable. Uninstall Claude Code following the setup documentation; plugins are disabled with /plugin commands inside Claude Code.

Security check

• The agent runs shell commands and modifies files
• The installer downloads and runs a script
• Code is sent to Anthropic models

README in short

Claude Code is an agentic coding tool that lives in the terminal and understands your codebase. The README lists installation methods for macOS, Linux and Windows and notes that npm installation is deprecated. The repository includes a set of plugins with commands and agents. Data collection, usage and privacy safeguards are described separately.

SKILL.md

---
name: frontend-design
description: Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
license: Complete terms in LICENSE.txt
---

# Frontend Design

Approach this as the design lead at a design studio known for giving every client a distinct visual identity that is not mistaken for anyone else's. This client has already rejected proposals that felt cliché or templated, and is paying for a distinctive point of view: make deliberate, opinionated choices about palette, typography, and layout that are specific to this brief, and take aesthetic risk if justified.

## Ground your designs in the subject matter

If the brief does not identify what the product or subject matter is, identify it yourself before designing, and confirm with the client. You can come up with one concrete subject, the design's audience, and the design's primary job, as a proposal. If there's any information in your memory about the client's preferences or context about what they're building, use that as a hint. The subject's industry, subject matter, materials, and vernacular are where distinctive visual choices come from — a design for a toy for girls aged 8–11 will be very aesthetically different from a dashboard for financial analysts. Build with the brief's real content and subject matter throughout.

## Design principles

For web designs, the hero is the first thing viewers will see. Open with the most characteristic thing in the subject's world, in the form that is most appropriate: a headline, an image, an animation, a live demo, an interactive moment, or other treatments. Be deliberate with your choice: a big number with a small label, supporting stats, and a gradient accent is the default treatment, so only use it if that's truly the best option.

Typography carries the personality of the page. You don't need a different typeface for display or headline text and body content: use one family or two, and if two, make them clearly distinct.

Related