testing-area 0.0.0-stage → 1.0.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/.agents/grimoire-skills.md +7 -0
- package/.agents/skills/analyze-layout-geometry/SKILL.md +62 -0
- package/.agents/skills/audit-existing-ui-component/SKILL.md +65 -0
- package/.agents/skills/optimize-responsive-layout/SKILL.md +63 -0
- package/.agents/skills/review-visual-consistency/SKILL.md +55 -0
- package/.agents/skills/validate-accessibility/SKILL.md +63 -0
- package/package.json +13 -4
- package/README.md +0 -3
|
@@ -0,0 +1,62 @@
|
|
|
1
|
+
---
|
|
2
|
+
id: analyze-layout-geometry
|
|
3
|
+
name: Analyze Layout Geometry
|
|
4
|
+
rank: C
|
|
5
|
+
version: 1.0.0
|
|
6
|
+
status: active
|
|
7
|
+
author: Dion
|
|
8
|
+
maintainers:
|
|
9
|
+
- Dion
|
|
10
|
+
contributors: []
|
|
11
|
+
created: 2026-10-17
|
|
12
|
+
updated: 2026-10-17
|
|
13
|
+
effort: low
|
|
14
|
+
estimated_tokens: 1000-2000
|
|
15
|
+
class: Validation / Audit
|
|
16
|
+
target: UI layout, screenshot, or component specification
|
|
17
|
+
tags: [ui, layout, geometry, spacing]
|
|
18
|
+
---
|
|
19
|
+
|
|
20
|
+
# Analyze Layout Geometry
|
|
21
|
+
|
|
22
|
+
## Attributes & Metadata
|
|
23
|
+
|
|
24
|
+
- **Rank:** C
|
|
25
|
+
- **Strategy:** Inspect, measure, report
|
|
26
|
+
- **Target:** UI layout, screenshot, or component specification
|
|
27
|
+
|
|
28
|
+
## Preconditions
|
|
29
|
+
|
|
30
|
+
- EXPECT a layout, screenshot, or component specification.
|
|
31
|
+
- ASSERT viewport dimensions and relevant design tokens when available.
|
|
32
|
+
- REJECT inputs without enough visual or structural information to assess geometry.
|
|
33
|
+
|
|
34
|
+
## Execution Pipeline
|
|
35
|
+
|
|
36
|
+
1. Identify containers, alignment axes, and layout boundaries.
|
|
37
|
+
2. Measure spacing, sizing, proportions, and gaps.
|
|
38
|
+
3. Compare values against stated or inferred design tokens.
|
|
39
|
+
4. Report inconsistencies and corrective changes.
|
|
40
|
+
|
|
41
|
+
## Core Effect
|
|
42
|
+
|
|
43
|
+
Produce a concise geometry assessment with actionable layout corrections.
|
|
44
|
+
|
|
45
|
+
## Constraints & Limits
|
|
46
|
+
|
|
47
|
+
- MUST distinguish measured values from estimates.
|
|
48
|
+
- MUST preserve intentional hierarchy and alignment.
|
|
49
|
+
- MUST NOT recommend arbitrary spacing without a stated basis.
|
|
50
|
+
- SHOULD identify the smallest structural change that resolves each issue.
|
|
51
|
+
|
|
52
|
+
## Example Invocation
|
|
53
|
+
|
|
54
|
+
**Input:** Apply this skill to a representative engineering request within its stated target.
|
|
55
|
+
|
|
56
|
+
**Output:** The defined artifact, verification results, and known limitations.
|
|
57
|
+
|
|
58
|
+
## Post-Execution Verification
|
|
59
|
+
|
|
60
|
+
- ENSURE every reported issue identifies its affected element.
|
|
61
|
+
- VERIFY recommendations address alignment, sizing, or spacing directly.
|
|
62
|
+
- EMIT findings grouped by severity and location.
|
|
@@ -0,0 +1,65 @@
|
|
|
1
|
+
---
|
|
2
|
+
id: audit-existing-ui-component
|
|
3
|
+
name: Audit Existing UI Component
|
|
4
|
+
rank: A
|
|
5
|
+
version: 1.0.0
|
|
6
|
+
status: active
|
|
7
|
+
author: Dion
|
|
8
|
+
maintainers:
|
|
9
|
+
- Dion
|
|
10
|
+
contributors: []
|
|
11
|
+
created: 2026-10-17
|
|
12
|
+
updated: 2026-10-17
|
|
13
|
+
effort: high
|
|
14
|
+
estimated_tokens: 4000-8000
|
|
15
|
+
class: Orchestration · Validation / Audit
|
|
16
|
+
target: Existing UI component or implementation
|
|
17
|
+
tags: [ui, audit, accessibility, responsive, consistency]
|
|
18
|
+
composes:
|
|
19
|
+
- analyze-layout-geometry
|
|
20
|
+
- validate-accessibility
|
|
21
|
+
- optimize-responsive-layout
|
|
22
|
+
- review-visual-consistency
|
|
23
|
+
---
|
|
24
|
+
|
|
25
|
+
# Audit Existing UI Component
|
|
26
|
+
|
|
27
|
+
## Prerequisites
|
|
28
|
+
|
|
29
|
+
- `analyze-layout-geometry` is available.
|
|
30
|
+
- `validate-accessibility` is available.
|
|
31
|
+
- `optimize-responsive-layout` is available.
|
|
32
|
+
- `review-visual-consistency` is available.
|
|
33
|
+
- The component implementation or rendered output is available.
|
|
34
|
+
- Supported viewports and project design references are known.
|
|
35
|
+
|
|
36
|
+
## Execution Pipeline
|
|
37
|
+
|
|
38
|
+
1. Analyze layout geometry and structural alignment.
|
|
39
|
+
2. Review visual consistency against project references.
|
|
40
|
+
3. Audit accessibility semantics and interaction behavior.
|
|
41
|
+
4. Check responsive behavior across supported viewports.
|
|
42
|
+
5. Consolidate findings by severity, effort, and dependency.
|
|
43
|
+
|
|
44
|
+
## Core Effect
|
|
45
|
+
|
|
46
|
+
Produce a prioritized engineering audit of an existing UI component.
|
|
47
|
+
|
|
48
|
+
## Constraints & Limits
|
|
49
|
+
|
|
50
|
+
- MUST preserve evidence from every composed skill.
|
|
51
|
+
- MUST separate observed defects from recommendations.
|
|
52
|
+
- MUST NOT claim compliance without sufficient inspection.
|
|
53
|
+
- SHOULD identify dependencies between corrective actions.
|
|
54
|
+
|
|
55
|
+
## Example Invocation
|
|
56
|
+
|
|
57
|
+
**Input:** Apply this skill to a representative engineering request within its stated target.
|
|
58
|
+
|
|
59
|
+
**Output:** The defined artifact, verification results, and known limitations.
|
|
60
|
+
|
|
61
|
+
## Post-Execution Verification
|
|
62
|
+
|
|
63
|
+
- ENSURE every finding has evidence, impact, and a recommended action.
|
|
64
|
+
- VERIFY duplicate findings are merged.
|
|
65
|
+
- EMIT a prioritized audit report and remaining limitations.
|
|
@@ -0,0 +1,63 @@
|
|
|
1
|
+
---
|
|
2
|
+
id: optimize-responsive-layout
|
|
3
|
+
name: Optimize Responsive Layout
|
|
4
|
+
rank: B
|
|
5
|
+
version: 1.0.0
|
|
6
|
+
status: active
|
|
7
|
+
author: Dion
|
|
8
|
+
maintainers:
|
|
9
|
+
- Dion
|
|
10
|
+
contributors: []
|
|
11
|
+
created: 2026-10-17
|
|
12
|
+
updated: 2026-10-17
|
|
13
|
+
effort: medium
|
|
14
|
+
estimated_tokens: 2000-4000
|
|
15
|
+
class: Transformation
|
|
16
|
+
target: Responsive UI implementation or layout specification
|
|
17
|
+
tags: [ui, responsive, layout, mobile]
|
|
18
|
+
---
|
|
19
|
+
|
|
20
|
+
# Optimize Responsive Layout
|
|
21
|
+
|
|
22
|
+
## Attributes & Metadata
|
|
23
|
+
|
|
24
|
+
- **Rank:** B
|
|
25
|
+
- **Strategy:** Inspect, model, adjust, verify
|
|
26
|
+
- **Target:** Responsive UI implementation or layout specification
|
|
27
|
+
|
|
28
|
+
## Preconditions
|
|
29
|
+
|
|
30
|
+
- EXPECT supported viewport ranges and primary content priorities.
|
|
31
|
+
- ASSERT the existing layout system, breakpoints, and design tokens when available.
|
|
32
|
+
- REJECT changes that optimize one viewport by breaking required content or behavior elsewhere.
|
|
33
|
+
|
|
34
|
+
## Execution Pipeline
|
|
35
|
+
|
|
36
|
+
1. Identify overflow, wrapping, collision, and hierarchy failures.
|
|
37
|
+
2. Define content-driven layout rules and breakpoint behavior.
|
|
38
|
+
3. Adjust containers, grids, flex rules, typography, and media sizing.
|
|
39
|
+
4. Verify key states across supported viewport ranges.
|
|
40
|
+
|
|
41
|
+
## Core Effect
|
|
42
|
+
|
|
43
|
+
Produce a responsive layout that preserves content hierarchy and interaction quality across viewport sizes.
|
|
44
|
+
|
|
45
|
+
## Constraints & Limits
|
|
46
|
+
|
|
47
|
+
- MUST prioritize content and interaction requirements over fixed dimensions.
|
|
48
|
+
- MUST preserve readable text and usable controls at supported sizes.
|
|
49
|
+
- MUST NOT add breakpoints without a layout failure or content requirement.
|
|
50
|
+
- SHOULD use fluid sizing before breakpoint-specific overrides.
|
|
51
|
+
|
|
52
|
+
## Example Invocation
|
|
53
|
+
|
|
54
|
+
**Input:** Apply this skill to a representative engineering request within its stated target.
|
|
55
|
+
|
|
56
|
+
**Output:** The defined artifact, verification results, and known limitations.
|
|
57
|
+
|
|
58
|
+
## Post-Execution Verification
|
|
59
|
+
|
|
60
|
+
- ENSURE no required content overflows or becomes inaccessible.
|
|
61
|
+
- VERIFY layout behavior at minimum, maximum, and intermediate widths.
|
|
62
|
+
- VERIFY touch targets, focus order, and text wrapping.
|
|
63
|
+
- EMIT changed rules, tested viewports, and remaining limitations.
|
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
---
|
|
2
|
+
id: review-visual-consistency
|
|
3
|
+
name: Review Visual Consistency
|
|
4
|
+
rank: C
|
|
5
|
+
version: 1.0.0
|
|
6
|
+
status: active
|
|
7
|
+
author: Dion
|
|
8
|
+
maintainers:
|
|
9
|
+
- Dion
|
|
10
|
+
contributors: []
|
|
11
|
+
created: 2026-10-17
|
|
12
|
+
updated: 2026-10-17
|
|
13
|
+
effort: low
|
|
14
|
+
estimated_tokens: 1000-2000
|
|
15
|
+
class: Validation / Audit
|
|
16
|
+
target: UI component, page, screenshot, or design reference
|
|
17
|
+
tags: [ui, visual, consistency, review]
|
|
18
|
+
---
|
|
19
|
+
|
|
20
|
+
# Review Visual Consistency
|
|
21
|
+
|
|
22
|
+
## Prerequisites
|
|
23
|
+
|
|
24
|
+
- EXPECT a UI artifact and a project reference, token set, or established component pattern.
|
|
25
|
+
- ASSERT the target viewport and relevant state when reviewing a rendered result.
|
|
26
|
+
|
|
27
|
+
## Execution Pipeline
|
|
28
|
+
|
|
29
|
+
1. Compare typography, color, spacing, borders, radii, elevation, and iconography.
|
|
30
|
+
2. Identify deviations from project patterns.
|
|
31
|
+
3. Classify deviations by visibility and user impact.
|
|
32
|
+
4. Recommend the smallest corrective changes.
|
|
33
|
+
|
|
34
|
+
## Core Effect
|
|
35
|
+
|
|
36
|
+
Produce a focused visual consistency review with actionable corrections.
|
|
37
|
+
|
|
38
|
+
## Constraints & Limits
|
|
39
|
+
|
|
40
|
+
- MUST distinguish visual defects from intentional variation.
|
|
41
|
+
- MUST use project references as the comparison basis.
|
|
42
|
+
- MUST NOT recommend changes without identifying the affected element.
|
|
43
|
+
- SHOULD prioritize repeated or high-visibility inconsistencies.
|
|
44
|
+
|
|
45
|
+
## Example Invocation
|
|
46
|
+
|
|
47
|
+
**Input:** Apply this skill to a representative engineering request within its stated target.
|
|
48
|
+
|
|
49
|
+
**Output:** The defined artifact, verification results, and known limitations.
|
|
50
|
+
|
|
51
|
+
## Post-Execution Verification
|
|
52
|
+
|
|
53
|
+
- ENSURE every finding includes location, evidence, and correction.
|
|
54
|
+
- VERIFY recommendations preserve hierarchy and usability.
|
|
55
|
+
- EMIT findings grouped by priority.
|
|
@@ -0,0 +1,63 @@
|
|
|
1
|
+
---
|
|
2
|
+
id: validate-accessibility
|
|
3
|
+
name: Validate Accessibility
|
|
4
|
+
rank: B
|
|
5
|
+
version: 1.0.0
|
|
6
|
+
status: active
|
|
7
|
+
author: Dion
|
|
8
|
+
maintainers:
|
|
9
|
+
- Dion
|
|
10
|
+
contributors: []
|
|
11
|
+
created: 2026-10-17
|
|
12
|
+
updated: 2026-10-17
|
|
13
|
+
effort: medium
|
|
14
|
+
estimated_tokens: 2000-4000
|
|
15
|
+
class: Validation / Audit
|
|
16
|
+
target: UI component, page, or interaction flow
|
|
17
|
+
tags: [ui, accessibility, semantics, keyboard]
|
|
18
|
+
---
|
|
19
|
+
|
|
20
|
+
# Validate Accessibility
|
|
21
|
+
|
|
22
|
+
## Attributes & Metadata
|
|
23
|
+
|
|
24
|
+
- **Rank:** B
|
|
25
|
+
- **Strategy:** Inspect, test, classify, remediate
|
|
26
|
+
- **Target:** UI component, page, or interaction flow
|
|
27
|
+
|
|
28
|
+
## Preconditions
|
|
29
|
+
|
|
30
|
+
- EXPECT component markup, implementation, or an accessible interaction description.
|
|
31
|
+
- ASSERT known user actions and supported states.
|
|
32
|
+
- REJECT claims of compliance without inspectable structure or behavior.
|
|
33
|
+
|
|
34
|
+
## Execution Pipeline
|
|
35
|
+
|
|
36
|
+
1. Inspect semantic structure, names, roles, and states.
|
|
37
|
+
2. Check keyboard navigation, focus order, and focus visibility.
|
|
38
|
+
3. Check labels, contrast, errors, status messages, and responsive zoom behavior.
|
|
39
|
+
4. Classify violations by impact and provide targeted fixes.
|
|
40
|
+
|
|
41
|
+
## Core Effect
|
|
42
|
+
|
|
43
|
+
Produce an accessibility assessment with concrete remediation steps.
|
|
44
|
+
|
|
45
|
+
## Constraints & Limits
|
|
46
|
+
|
|
47
|
+
- MUST prefer native HTML semantics over unnecessary ARIA.
|
|
48
|
+
- MUST ensure every interactive control has an accessible name.
|
|
49
|
+
- MUST support keyboard operation for all essential actions.
|
|
50
|
+
- MUST NOT claim full compliance from static inspection alone.
|
|
51
|
+
- SHOULD identify the applicable WCAG criterion when known.
|
|
52
|
+
|
|
53
|
+
## Example Invocation
|
|
54
|
+
|
|
55
|
+
**Input:** Apply this skill to a representative engineering request within its stated target.
|
|
56
|
+
|
|
57
|
+
**Output:** The defined artifact, verification results, and known limitations.
|
|
58
|
+
|
|
59
|
+
## Post-Execution Verification
|
|
60
|
+
|
|
61
|
+
- ENSURE each finding includes impact, location, and remediation.
|
|
62
|
+
- VERIFY all essential actions have a keyboard path.
|
|
63
|
+
- EMIT findings grouped by severity and verification method.
|
package/package.json
CHANGED
|
@@ -1,6 +1,15 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "testing-area",
|
|
3
|
-
"version": "
|
|
4
|
-
"
|
|
5
|
-
"
|
|
6
|
-
|
|
3
|
+
"version": "1.0.0",
|
|
4
|
+
"description": "",
|
|
5
|
+
"main": "index.js",
|
|
6
|
+
"scripts": {
|
|
7
|
+
"test": "echo \"Error: no test specified\" && exit 1"
|
|
8
|
+
},
|
|
9
|
+
"keywords": [],
|
|
10
|
+
"author": "",
|
|
11
|
+
"license": "ISC",
|
|
12
|
+
"dependencies": {
|
|
13
|
+
"engineering-grimoires": "file:.."
|
|
14
|
+
}
|
|
15
|
+
}
|
package/README.md
DELETED