home / skills / dropseed / plain / plain-install

plain-install skill

safe

This skill guides installing Plain packages and completing their setup, including documentation steps and optional dev-only adjustments.

npx playbooks add skill dropseed/plain --skill plain-install

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

746 B

---
name: plain-install
description: Installs Plain packages and guides through setup steps. Use when adding new packages to a project.
---

# Install Plain Packages

## 1. Install the package(s)

```
uv run plain install <package-name> [additional-packages...]
```

## 2. Complete setup for each package

1. Run `uv run plain docs <package>` and read the installation instructions
2. If the docs indicate it's a dev tool, move it: `uv remove <package> && uv add <package> --dev`
3. Complete any code modifications from the installation instructions

## Guidelines

- DO NOT commit any changes
- Report back with:
    - Whether setup completed successfully
    - Any manual steps the user needs to complete
    - Any issues or errors encountered

Overview

This skill installs Plain packages into a project and guides you through the required setup steps. It runs the package installer, opens the package documentation for any post-install tasks, and reports any manual actions or errors. Use it to add new functionality without guessing about required configuration.

How this skill works

The skill runs the Plain package installer command and then fetches the package-specific installation docs. It identifies whether the package should be a dev dependency and suggests moving it when appropriate. Finally, it lists code changes the docs recommend and prompts you to apply them, then summarizes success, remaining manual steps, and any errors.

When to use it

Adding a new Plain package to an existing project
Installing multiple Plain packages at once
Setting up tools that may require dev-only install flags
Verifying post-install configuration steps for a package
Onboarding a package with documented manual code changes

Best practices

Run uv run plain install from your project root to ensure paths resolve correctly
After install, run uv run plain docs <package> and read instructions before committing changes
If a package is a development tool, move it with uv remove <pkg> && uv add <pkg> --dev
Do not commit install-related changes until you confirm the setup is complete
Document any manual code edits and test the app after applying recommended modifications

Example use cases

Install a new web middleware and follow documentation to add initialization code
Add a testing or linting tool as a dev dependency and apply its setup steps
Batch-install several packages and collect per-package post-install actions
Validate that a package’s manual patch or config entry was applied correctly
Report back to a teammate with a concise list of remaining manual steps and any errors

FAQ

Will this skill commit changes to my repository?

No. The workflow explicitly avoids committing any changes. You should review and commit after verifying the setup.

How do I mark a package as a dev dependency?

If the package docs indicate it’s a dev tool, move it with: uv remove <package> && uv add <package> --dev. The skill will flag packages that need this change.