frontend-precision 0.0.0-stage → 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,3 +1,46 @@
1
- # Temporary Holding Version
1
+ # frontend-precision
2
2
 
3
- This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
3
+ Cursor-first frontend precision toolkit: Playwright screenshots, pixel visual diff, configured test runs, and JSON/Markdown/HTML reports.
4
+
5
+ ## Install
6
+
7
+ This package is not yet published to the npm registry. Install it from a
8
+ local checkout or a generated tarball:
9
+
10
+ ```bash
11
+ pnpm add -D /absolute/path/to/frontend-precision/packages/cli
12
+ pnpm exec frontend-precision init
13
+ pnpm exec playwright install chromium
14
+ ```
15
+
16
+ After an npm release is verified, the supported registry command will be:
17
+
18
+ ```bash
19
+ pnpm add -D frontend-precision
20
+ ```
21
+
22
+ ## Commands
23
+
24
+ | Command | Purpose |
25
+ |---|---|
26
+ | `init` | Create config, Cursor Skill, rules, and templates (does not overwrite by default) |
27
+ | `doctor` | Check Node, pnpm, config, baseUrl (2xx), references, Playwright, Skill |
28
+ | `capture` | Screenshot configured routes |
29
+ | `visual` | Compare screenshots to reference PNGs |
30
+ | `test` | Run `testCommand` (and optional checks) and record results |
31
+ | `report` | Aggregate capture/visual/test into `report.json` / `.md` / `.html` |
32
+
33
+ Typical verify loop:
34
+
35
+ ```bash
36
+ frontend-precision capture --run-id <id>
37
+ frontend-precision visual --run-id <id>
38
+ frontend-precision test --run-id <id>
39
+ frontend-precision report --run-id <id>
40
+ ```
41
+
42
+ Overall `report` status is `PASS` only when capture, visual, and tests all completed successfully. Missing stages yield `SKIPPED`; failures yield `FAIL`; `fixAttempts > maxFixAttempts` yields `BLOCKED`.
43
+
44
+ ## Docs
45
+
46
+ See the repository root README for Skill workflow, Figma MCP notes, and the Vite demo walkthrough.
@@ -0,0 +1,2 @@
1
+
2
+ export { }