@next-friday/create-app 9.1.0 → 9.1.1

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.
Files changed (4) hide show
  1. package/package.json +2 -1
  2. package/templates/base/.agents/skills/sdlc/playbooks/design.md +2 -2
  3. package/templates/base/.claude/skills/sdlc/playbooks/design.md +2 -2
  4. package/templates/base/.cursor/skills/sdlc/playbooks/design.md +2 -2
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@next-friday/create-app",
3
- "version": "9.1.0",
3
+ "version": "9.1.1",
4
4
  "description": "Create a Next Friday project from a template.",
5
5
  "keywords": [
6
6
  "create",
@@ -80,6 +80,7 @@
80
80
  "knip": "knip",
81
81
  "lint": "eslint . --fix --cache --max-warnings=0 --no-inline-config",
82
82
  "lint:check": "eslint . --cache --max-warnings=0 --no-inline-config",
83
+ "loop:measure": "node scripts/measure-loop.ts",
83
84
  "rules:check": "node scripts/sync-agent-rules.ts --check",
84
85
  "rules:sync": "node scripts/sync-agent-rules.ts",
85
86
  "sort-package-json": "sort-package-json package.json",
package/templates/base/.agents/skills/sdlc/playbooks/design.md CHANGED
@@ -8,7 +8,7 @@ This playbook turns a merged intent into the requirements and design spec.
8
8
  - `spec.md` already exists: say so and name the file.
9
9
  2. Read the four policies, every time, before you write: `.agents/skills/brand-policy/SKILL.md`, `.agents/skills/security-policy/SKILL.md`, `.agents/skills/compliance-policy/SKILL.md`, and `.agents/skills/ux-policy/SKILL.md`. Then read the code and the docs the change touches.
10
10
  3. Write `intent/<change>/spec.md` from the template below, in the language of the files already in `intent/`. Use exactly the template's headings.
11
- - **Request:** under the status line, quote the words of the request that started this spec. Add no date and no commit: git records both.
11
+ - **Request:** under the status line, quote the words of the request that started this spec. End the line with the template's "Skills at" sentence; its commit is the output of `git log -1 --format=%h -- .agents/skills`.
12
12
  - **Requirements:** numbered. Each one states a result a test or a reader can check.
13
13
  - **Design:** how the change fits the existing code: the files that change, and what each one does afterwards.
14
14
  - **Policies:** one line for each of the four policies. State which rules of that policy the change must meet, each as a requirement number, or write "Does not apply" and why.
@@ -26,7 +26,7 @@ This playbook turns a merged intent into the requirements and design spec.
26
26
 
27
27
  From `intent/<change>/intent.md`. Status: draft.
28
28
 
29
- Request: "<the words of the request that started this spec>".
29
+ Request: "<the words of the request that started this spec>". Skills at `<commit>`.
30
30
 
31
31
  ## Requirements
32
32
 
package/templates/base/.claude/skills/sdlc/playbooks/design.md CHANGED
@@ -8,7 +8,7 @@ This playbook turns a merged intent into the requirements and design spec.
8
8
  - `spec.md` already exists: say so and name the file.
9
9
  2. Read the four policies, every time, before you write: `.agents/skills/brand-policy/SKILL.md`, `.agents/skills/security-policy/SKILL.md`, `.agents/skills/compliance-policy/SKILL.md`, and `.agents/skills/ux-policy/SKILL.md`. Then read the code and the docs the change touches.
10
10
  3. Write `intent/<change>/spec.md` from the template below, in the language of the files already in `intent/`. Use exactly the template's headings.
11
- - **Request:** under the status line, quote the words of the request that started this spec. Add no date and no commit: git records both.
11
+ - **Request:** under the status line, quote the words of the request that started this spec. End the line with the template's "Skills at" sentence; its commit is the output of `git log -1 --format=%h -- .agents/skills`.
12
12
  - **Requirements:** numbered. Each one states a result a test or a reader can check.
13
13
  - **Design:** how the change fits the existing code: the files that change, and what each one does afterwards.
14
14
  - **Policies:** one line for each of the four policies. State which rules of that policy the change must meet, each as a requirement number, or write "Does not apply" and why.
@@ -26,7 +26,7 @@ This playbook turns a merged intent into the requirements and design spec.
26
26
 
27
27
  From `intent/<change>/intent.md`. Status: draft.
28
28
 
29
- Request: "<the words of the request that started this spec>".
29
+ Request: "<the words of the request that started this spec>". Skills at `<commit>`.
30
30
 
31
31
  ## Requirements
32
32
 
package/templates/base/.cursor/skills/sdlc/playbooks/design.md CHANGED
@@ -8,7 +8,7 @@ This playbook turns a merged intent into the requirements and design spec.
8
8
  - `spec.md` already exists: say so and name the file.
9
9
  2. Read the four policies, every time, before you write: `.agents/skills/brand-policy/SKILL.md`, `.agents/skills/security-policy/SKILL.md`, `.agents/skills/compliance-policy/SKILL.md`, and `.agents/skills/ux-policy/SKILL.md`. Then read the code and the docs the change touches.
10
10
  3. Write `intent/<change>/spec.md` from the template below, in the language of the files already in `intent/`. Use exactly the template's headings.
11
- - **Request:** under the status line, quote the words of the request that started this spec. Add no date and no commit: git records both.
11
+ - **Request:** under the status line, quote the words of the request that started this spec. End the line with the template's "Skills at" sentence; its commit is the output of `git log -1 --format=%h -- .agents/skills`.
12
12
  - **Requirements:** numbered. Each one states a result a test or a reader can check.
13
13
  - **Design:** how the change fits the existing code: the files that change, and what each one does afterwards.
14
14
  - **Policies:** one line for each of the four policies. State which rules of that policy the change must meet, each as a requirement number, or write "Does not apply" and why.
@@ -26,7 +26,7 @@ This playbook turns a merged intent into the requirements and design spec.
26
26
 
27
27
  From `intent/<change>/intent.md`. Status: draft.
28
28
 
29
- Request: "<the words of the request that started this spec>".
29
+ Request: "<the words of the request that started this spec>". Skills at `<commit>`.
30
30
 
31
31
  ## Requirements
32
32