agentsclimarketplace

Understand propose implement verify

Skill pekral/cursor-rules/skills/understand-propose-implement-verify

PHP and Laravel Cursor rules — coding standards, testing, and conventions for the Cursor editor. Install via Composer.

Install
npx -y skills add pekral/cursor-rules --skill understand-propose-implement-verify

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when following a strict problem-solving loop: understand, propose, implement, verify.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.0 KB, 408 tokens by cl100k_base, as published. Nobody here has run it

Constraints

  • Apply @rules/php/core-standards.mdc only once it is established that the project is a PHP project (PHP stack in composer.json) and the change touches PHP code — skip it for non-PHP work (docs, tooling, infra, config); do not load the PHP standards for a task that does not touch PHP.
  • If the current project uses Laravel, also apply @rules/laravel/laravel.mdc, @rules/laravel/architecture.mdc, @rules/laravel/filament.mdc, and @rules/laravel/livewire.mdc (likewise only when the change touches PHP)
  • Always follow this order: understand → propose → implement → verify
  • Prefer existing project skills over custom solutions; do not duplicate logic already covered by a skill

Use when

  • Solving a task that requires structured thinking and controlled execution
  • Coordinating multiple steps or skills

Execution

1. Understand

  • Analyze the problem, context, and related resources
  • Classify the task (bug, feature, refactor, review, etc.)
  • Define a short checklist of goals, constraints, and assumptions

2. Propose

  • Suggest the smallest safe solution
  • Explain why this approach is preferred (impact, risk, trade-offs)
  • Select relevant existing skills to execute the plan

3. Implement

  • Execute the solution using selected skills where applicable
  • Keep changes focused and aligned with project conventions
  • Add or update tests for changed behavior

4. Verify

  • Validate the result against requirements
  • Run relevant checks/tests for the affected scope
  • Ensure no regressions or unintended side effects
  • Summarize what was changed, tested, and any remaining risks

Done when

  • The task is fully addressed
  • The solution follows the defined loop
  • Existing skills were reused where applicable
  • Results are validated and clearly summarized

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,984. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.