frontend-assessment-skill 1.0.8 → 1.0.9
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/package.json +1 -1
- package/skills/SKILL.md +8 -5
package/package.json
CHANGED
package/skills/SKILL.md
CHANGED
|
@@ -275,11 +275,14 @@ List the five most significant cons in ranked order:
|
|
|
275
275
|
|
|
276
276
|
### Frontend business logic diagram
|
|
277
277
|
|
|
278
|
-
Include a low-level Mermaid `flowchart` tracing
|
|
279
|
-
|
|
280
|
-
- Inspect
|
|
281
|
-
-
|
|
282
|
-
-
|
|
278
|
+
Include a low-level Mermaid `flowchart` tracing representative frontend business flows from routes/pages and user actions through components, state management, domain logic, and API/data-access layers to data sources and endpoints. Make request, response, and state-update directions explicit.
|
|
279
|
+
|
|
280
|
+
- Inspect frontend source, routing, state/data-fetching code, API clients, and configuration. Represent only verified flows; label unknowns and do not infer behavior from names alone.
|
|
281
|
+
- Distinguish the frontend, backend/services in the same repository (including other monorepo packages), and services outside the repository. Show external service/API endpoint names or base URLs when discoverable. If configured via an environment variable, show its name but never its secret value; mark the destination unresolved when it cannot be determined.
|
|
282
|
+
- Connect authentication to the requests it protects: show how tokens/credentials are acquired, passed through the API client or auth wrapper, and attached to protected requests only when confirmed by code. Do not leave auth nodes disconnected from the API flow.
|
|
283
|
+
- Draw request edges from the caller/client to the endpoint and separate response edges back to the data-access/state layer. Label each with the verified HTTP method and route where available. Do not use a generic API node as an ambiguous hub for unrelated calls; group routes under a service only when their shared base/service is verified, and keep endpoint/request nodes distinct enough to trace each flow.
|
|
284
|
+
- Show branching, retries, redirects, fallbacks, and error paths only when verified. Distinguish a configured base URL from the routes appended to it; do not imply a fallback or route transformation unless implementation confirms it.
|
|
285
|
+
- Keep the diagram focused on business logic and data flow rather than a generic infrastructure overview. Use unique Mermaid node IDs and valid Mermaid flowchart syntax in a fenced `mermaid` block; avoid overly dense diagrams by grouping related operations where their relationships remain clear.
|
|
283
286
|
|
|
284
287
|
### Verdict
|
|
285
288
|
|