skillshare implement feature

Engineering Community

Skill notes

Step 1: Understand Requirements

If $ARGUMENTS is a file path: Read the spec file Extract acceptance criteria and edge cases Identify affected packages If $ARGUMENTS is a description:

Step 2: Identify Affected Files

List all files that will be created or modified: Display the file list and continue. If scope is unclear, ask the user.

Step 3: Write Failing Tests First (RED)

Write integration tests using testutil.Sandbox: Verify tests fail:

Step 4: Implement (GREEN)

Write minimal code to make tests pass: Follow existing patterns in cmd/skillshare/ and internal/ Use internal/ui for terminal output (colors, spinners, boxes) Add oplog instrumentation for mutating commands: Register command in main.go commands map if new command

Step 5: Refactor and Verify

Clean up code while keeping tests green Run full quality check: Fix any formatting or lint issues

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@runkids · no license declared
Token usage
Lean
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Understand Requirements

If $ARGUMENTS is a file path: Read the spec file Extract acceptance criteria and edge cases Identify affected packages If $ARGUMENTS is a description:

02
Step 2: Identify Affected Files

List all files that will be created or modified: Display the file list and continue. If scope is unclear, ask the user.

03
Step 3: Write Failing Tests First (RED)

Write integration tests using `testutil.Sandbox`: Verify tests fail:

04
Step 4: Implement (GREEN)

Write minimal code to make tests pass: Follow existing patterns in `cmd/skillshare/` and `internal/` Use `internal/ui` for terminal output (colors, spinners, boxes) Add oplog instrumentation for mutating commands: Register command in `main.go` commands map if new command

05
Step 5: Refactor and Verify

Clean up code while keeping tests green Run full quality check: Fix any formatting or lint issues

06
Step 6: E2E Runbook (Major Features Only)

If the feature meets any of these criteria, generate an E2E runbook: New command or subcommand Changes to install/uninstall/sync flow Security-related (audit, hash verification, rollback) Multi-step user workflow (init → install → sync → verify)

07
Step 7: Stage and Report

List all created/modified files Confirm each acceptance criterion is met with test evidence Remind user to run `update-docs` if the feature affects CLI flags or user-visible behavior

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.