Skip to content
Back to search

lwh

MarketplaceWorks with Claude CodeGitHub

Skills that help people plan, build and test real apps with Claude Code, learning as they go.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked yesterday
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/hassancs91--lwh-ai-coding-skills/badge.svg)](/listings/hassancs91--lwh-ai-coding-skills)

HTML

<a href="/listings/hassancs91--lwh-ai-coding-skills"><img src="/api/listings/hassancs91--lwh-ai-coding-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Pick one way. Installing both gives you every command twice.

With one command (recommended)

Needs [Node.js](https://nodejs.org). In a terminal:

npx skills add hassancs91/lwh-ai-coding-skills -g -a claude-code

Choose all the skills when it asks. `-g` installs them for every project; leave it out to install them only in the folder you are in. Then restart Claude Code.

**Update:** run `npx skills update`. Run `npx skills check` to see whether there is an update.

As a Claude Code plugin

In Claude Code:

/plugin marketplace add hassancs91/lwh-ai-coding-skills
/plugin install lwh-ai-coding@lwh

The second line opens the plugin's page, where you choose where to install it and confirm. It also installs `lwh-core`, the plugin that holds `/lwh-run` and `/lwh-stop`. Then run `/reload-plugins`.

Claude Code lists a plugin's commands with the plugin's name in front, such as `/lwh-ai-coding:lwh-plan-app`. Typing the short name, `/lwh-plan-app`, runs the same command.

**Get updates automatically:** run `/plugin`, open **Marketplaces**, choose **lwh**, and turn on auto-update.

**Update by hand:** run `/plugin marketplace update lwh`, then run `/plugin`, open **Installed**, choose the plugin and select **Update now**. The new version loads in your next session, or after `/reload-plugins`.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 21 lines
  1. {
  2. "name": "lwh",
  3. "owner": {
  4. "name": "Hasan Aboul Hasan"
  5. },
  6. "description": "Skills that help people plan, build and test real apps with Claude Code, learning as they go.",
  7. "plugins": [
  8. {
  9. "name": "lwh-core",
  10. "source": "./plugins/lwh-core",
  11. "description": "Run any list of tasks to completion with a chain of worker subagents, and stop a run cleanly at any time.",
  12. "category": "productivity"
  13. },
  14. {
  15. "name": "lwh-ai-coding",
  16. "source": "./plugins/lwh-ai-coding",
  17. "description": "Plan an app, stress-test the plan, design its screens, split it into tested tasks, and security-check the result. Installs lwh-core to run the tasks.",
  18. "category": "development"
  19. }
  20. ]
  21. }
README.md · README · 107 lines
  1. # lwh skills for Claude Code
  2. Claude Code skills that take you from an app idea to a built, tested app, and teach you the building blocks of a solid app along the way.
  3. - **Planning and checking:** plan the app with you, look for holes in the plan, design its screens, split it into small tested tasks, and check its security.
  4. - **Running:** `/lwh-run` gets any list of tasks done with a chain of workers that hand off to each other, so long runs stay reliable. It works with these skills, and on its own with any task list.
  5. Every decision stays yours. The skills explain each choice, recommend one, and let you pick, or say "decide the rest".
  6. **Early release, version 0.1.0.** Tested on Claude Code 2.1.319. Expect rough edges, and please [report what you find](#report-a-problem).
  7. ## Install
  8. Pick one way. Installing both gives you every command twice.
  9. ### With one command (recommended)
  10. Needs [Node.js](https://nodejs.org). In a terminal:
  11. ```
  12. npx skills add hassancs91/lwh-ai-coding-skills -g -a claude-code
  13. ```
  14. Choose all the skills when it asks. `-g` installs them for every project; leave it out to install them only in the folder you are in. Then restart Claude Code.
  15. **Update:** run `npx skills update`. Run `npx skills check` to see whether there is an update.
  16. ### As a Claude Code plugin
  17. In Claude Code:
  18. ```
  19. /plugin marketplace add hassancs91/lwh-ai-coding-skills
  20. /plugin install lwh-ai-coding@lwh
  21. ```
  22. The second line opens the plugin's page, where you choose where to install it and confirm. It also installs `lwh-core`, the plugin that holds `/lwh-run` and `/lwh-stop`. Then run `/reload-plugins`.
  23. Claude Code lists a plugin's commands with the plugin's name in front, such as `/lwh-ai-coding:lwh-plan-app`. Typing the short name, `/lwh-plan-app`, runs the same command.
  24. **Get updates automatically:** run `/plugin`, open **Marketplaces**, choose **lwh**, and turn on auto-update.
  25. **Update by hand:** run `/plugin marketplace update lwh`, then run `/plugin`, open **Installed**, choose the plugin and select **Update now**. The new version loads in your next session, or after `/reload-plugins`.
  26. ## Start
  27. 1. Make a new, empty folder for your app.
  28. 2. Open Claude Code in that folder. Not in your home folder or on the Desktop.
  29. 3. Run `/lwh-plan-app`, or `/lwh-guide` for a short tour first.
  30. Each command ends by telling you the next one. `/lwh-whats-next` tells you where you are at any time.
  31. | Command | What it does |
  32. |---|---|
  33. | `/lwh-plan-app` | An interview that turns your idea into a written plan, at the pace you choose |
  34. | `/lwh-challenge-plan` | Looks for holes in the plan and fixes them, after `/clear` |
  35. | `/lwh-design` | Builds real mockups of your screens to choose from, then writes the design the build follows. Recommended, not required |
  36. | `/lwh-make-tasks` | Splits the plan into small tasks, each with its tests |
  37. | `/lwh-run` | Gets the tasks done: one, a few, a milestone, or all of them |
  38. | `/lwh-stop` | Stops a run cleanly. Run it from a second window |
  39. | `/lwh-security-check` | Attacks the app to find security problems, reports them as high, medium and low, and fixes the ones you choose |
  40. | `/lwh-whats-next` | Where the project stands, and the command to run next |
  41. | `/lwh-guide` | A short tour, and answers to questions about the skills |
  42. ## What a run needs from you
  43. - **Git, and your stack's tools** (such as Node or Python) installed. `/lwh-run` checks, and tells you the exact command for anything missing.
  44. - **A few answers before it starts:** how far to go, when to pause, the accounts or keys only you can create, and a spending limit for any paid service.
  45. - **The window open and the computer awake.** A run pauses whenever a permission prompt appears. `/lwh-run` offers a few narrow allow rules so that happens less.
  46. - **Time and usage.** A long run can use a large share of your plan's usage. You choose how far each run goes, so start with one milestone. Mockups take time too: one app with 21 screens took 83 minutes, which is why `/lwh-design` offers to mock up only the main screens of a big app.
  47. Work happens on a branch called `lwh/work`. Nothing is pushed or deployed. At the end, the run offers to merge the branch on your computer.
  48. These skills do not put your app online yet. The plan lists what is needed before real users, under "Before going live".
  49. ## Report a problem
  50. Open an issue at https://github.com/hassancs91/lwh-ai-coding-skills/issues and say:
  51. - which command you ran, what happened, and what you expected
  52. - how you installed: with `npx skills` or as a plugin
  53. - your Claude Code version, from `claude --version`
  54. Never paste a key or a password into an issue.
  55. ## Try it from a local copy
  56. Open Claude Code in a new, empty folder with the skills loaded from this folder, for this session only:
  57. ```
  58. claude --plugin-dir <path-to-this-folder>/plugins/lwh-ai-coding --plugin-dir <path-to-this-folder>/plugins/lwh-core
  59. ```
  60. Then run `/lwh-plan-app`. Edits to the skills take effect after `/reload-plugins` or a restart.
  61. ## Change the skills
  62. - [docs/file-contract.md](docs/file-contract.md) defines every file the skills read and write. If a skill and the contract disagree, the contract wins.
  63. - Every skill is self-contained: it reads only its own folder, so it works when installed on its own with `npx skills`. Files that several skills need are copied into each one by the two scripts below.
  64. - How the skills talk to users lives in `shared/house-style.md`. Edit it there, then run `node scripts/sync-shared.mjs` to copy it into every skill.
  65. - The blocks live in `scripts/blocks-meta.json`. Edit it there, then run `node scripts/build-blocks.mjs`, which checks every field and rebuilds the `blocks/` folder of each skill that reads them. Never edit those folders by hand.
  66. - Before a release, run `node scripts/sync-shared.mjs --check` and `node scripts/build-blocks.mjs --check`, then bump `version` in each plugin's `plugin.json` and tag the commit.
  67. - `main` gets release commits only. Plugin users get a change when the version changes, but `npx skills update` takes whatever is on `main`.
  68. ## License
  69. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.