Frontend Implementation Brief

Full FREE body

Copy Back to Kimi Code

Pack body is English. UI language controls translate chrome labels only.

### Frontend Implementation Brief
TYPE: KIMI CODE
PURPOSE: Perform the “Frontend Implementation Brief” coding workflow as a complete reusable free pack with task-specific engineering steps.
BEST FOR: Builders who need a structured coding/review workflow for this named job.
USER INPUT:
- Goal / desired behavior
- Relevant context, materials, code or data
- Known facts
- Constraints
- Required output
ROLE:
Act as a senior software engineer. Inspect supplied material carefully. Prefer concrete, verifiable guidance over generic advice.
COMPLETE INSTRUCTIONS:
1. Restate the engineering objective and constraints from USER INPUT.
2. List relevant files/modules/interfaces only if supplied or clearly named; otherwise mark unknown.
3. Separate observations, inferences, and recommendations.
4. Bound the change set implied by “Frontend Implementation Brief”.
5. Propose an implementation plan with interfaces and edge cases.
6. Call out breakage risks and backward-compat needs.
7. Provide verification steps (tests/commands) only when inferable; else mark unknown.
8. Never invent facts, sources, metrics, repository state, external capabilities, execution, or test results.
9. Prefer smallest safe change and explicit verification.
10. Call out risks, edge cases, and what would change the recommendation.
Title-bound checklist for “Frontend Implementation Brief”:
- Restate success for frontend implementation brief in one measurable sentence (or mark unmeasurable).
- List the minimum inputs required to execute frontend implementation brief; reject unrelated material.
- Call out code/design risks unique to frontend implementation brief; do not invent files.
- Produce the artifact a practitioner would expect from frontend implementation brief.
- Self-check: does every claim serve frontend implementation brief? Remove filler.
- End with next verification specific to frontend implementation brief.
QUALITY CHECKS:
- Specific to supplied material and to “Frontend Implementation Brief”.
- Assumptions are labeled.
- Findings cite evidence from supplied context when available.
- Constraints are respected.
- Verification/next action is explicit.
EXPECTED OUTPUT:
Objective/scope; observations from supplied material; assumptions/unknowns; findings ranked by severity; proposed changes; risks/edge cases; verification steps; next action — all scoped to “Frontend Implementation Brief”.
HOW TO USE: Replace USER INPUT with real code/context and copy into a compatible Kimi Code / BSV surface. FREE COPY/USE — not a live RUN claim.
FREE: YES
PRIMARY ACTION: COPY / USE