fictjs/fict-best-practices
packages/skill/skills/fict-best-practices/SKILL.md
Fict compiler and runtime engineering guide for correctness and reliability. Use when implementing or reviewing Fict compiler transforms, runtime reactivity behavior, SSR/resume flow, devtools/playground integration, or release CI gates in Fict repositories.
$ install --global
skillsauthnpx skillsauth add fictjs/fict fict-best-practicesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 4, 2026, 10:30 PM39.4s20 files scanned
SKILL.md
- name:
- fict-best-practices
- description:
- Fict compiler and runtime engineering guide for correctness and reliability. Use when implementing or reviewing Fict compiler transforms, runtime reactivity behavior, SSR/resume flow, devtools/playground integration, or release CI gates in Fict repositories.
Fict Compiler and Runtime Best Practices
Production-focused guidance for engineering tasks across Fict compiler, runtime, SSR, devtools, and release workflows. Rules are optimized for AI agents doing code changes and reviews under correctness and regression-risk constraints.
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
| -------- | ----------------------------------- | -------- | ------------- |
| 1 | Compiler Guarantees | CRITICAL | compiler- |
| 2 | Reactivity Semantics | CRITICAL | reactivity- |
| 3 | Runtime Safety and Performance | HIGH | runtime- |
| 4 | SSR and Resume Stability | HIGH | ssr- |
| 5 | Tooling and DX Boundaries | MEDIUM | tooling- |
| 6 | Verification and Release Discipline | CRITICAL | quality- |
Quick Reference
1. Compiler Guarantees (CRITICAL)
compiler-strict-guarantee-ci- Enforce fail-closed guarantee mode in CIcompiler-macro-placement-top-level- Keep macros at top-level component or hook scopecompiler-fail-closed-diagnostics- Treat fallback diagnostics as blockers
2. Reactivity Semantics (CRITICAL)
reactivity-derived-values- Rely on compiler-derived memoization and avoid stale snapshotsreactivity-no-state-escape- Prevent state lifetime escape outside owning scopereactivity-props-shaping- Keep props/reactive object shaping analyzable
3. Runtime Safety and Performance (HIGH)
runtime-shared-state-primitives- Use$store/createSignalfor shared state boundariesruntime-effect-cleanup- Always return cleanup for subscriptions and async side effectsruntime-no-side-effects-in-memo- Keep memo bodies pure and move effects to$effect
4. SSR and Resume Stability (HIGH)
ssr-resource-keying- Key resources and align Suspense boundaries with async ownershipssr-resume-snapshot-contract- Preserve snapshot schema and loader failure semantics
5. Tooling and DX Boundaries (MEDIUM)
tooling-devtools-dev-only- Keep devtools instrumentation development-onlytooling-playground-runtime-isolation- Isolate playground features from production runtime code paths
6. Verification and Release Discipline (CRITICAL)
quality-regression-tests-for-bugs- Add minimal regression tests for every fixed defectquality-release-gates- Run compiler/runtime gates before merge or release
How to Use
Read rule files in rules/ for detailed explanations and bad/good examples.
Use AGENTS.md when you want a single compiled document with all rules.
Full Compiled Document
AGENTS.md
Related Skills
fictjs/fict-devtools-playground
tools
VerifiedTrustedCommunity
Fict DevTools and Playground engineering guide. Use when implementing, debugging, or reviewing Fict devtools panel/extension behavior, signal/computed/effect inspection UX, graph/timeline interactions, or playground preview refresh and isolation from production runtime.
61SKILL.mdUpdated Apr 4, 2026
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,764SKILL.mdUpdated Apr 10, 2026
steipete/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,588SKILL.mdUpdated Apr 13, 2026