factorialco/factorial-code-skills
Reference implementations for Factorial Code — a complete marketplace payroll integration, a custom app with full install/uninstall lifecycle, and utility processes.
npx skills add factorialco/factorial-code-skills --skill fcode-examples
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Framework (OSS). Expo's official example projects - the expo/examples repo of ~70 `with-*` inte…
251 installsHow to inject external code examples into Dartdoc using the {@example} directive, and how to fi…
118 installsCurated prompt and usage examples for research, portfolio review, quote requests, approval-gate…
8.8K installsHow to inject external code examples into Dartdoc using the {@example} directive, and how to fi…
87 installsFind working Deepgram integration examples with third-party platforms and frameworks. Use whene…
269 installsRun python examples in auto mode with logging, rerun helpers, and background control.
140 installsOther skills from factorialco/factorial-code-skills · top by installs.
npx skills add factorialco/factorial-code-skills
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
main
Parsed from SKILL.md frontmatter.
Files included with this skill beyond the listing page.
SKILL.md
4,580 B
SUMMARY.md
383 B
Worked, production-shaped examples of complete Factorial Code apps. Each reference in references/ walks through one real sample: its architecture, the key code, and how to adapt it. They complement the rule-focused skills (fcode-core-concepts, fcode-javascript/fcode-python, fcode-json-schema, fcode-forms, fcode-cli): those tell you how to write fcode code, this one shows what a finished app looks like.
Adapt, don't paste. These are patterns to rebuild for the user's actual vendor/requirements — rename slugs, variables, and mappings; drop what the use case doesn't need.
| You are building… | Read |
|---|---|
| A marketplace integration that delivers Factorial data (payroll, leaves, …) to an external system | [references/integration-acme.md](references/integration-acme.md) |
| A custom app with install/uninstall lifecycle: setup form, webhooks, schedules | [references/custom-app-linear.md](references/custom-app-linear.md) |
| A one-shot automation: export/report generation, file processing | [references/utility-processes.md](references/utility-processes.md) |
Where to find a specific pattern, regardless of which app you build:
| Pattern | Reference |
|---|---|
Extending the outbound-sync base class (OutboundSync) |
integration-acme |
| Per-item API push vs aggregate-to-file delivery | integration-acme |
Reporting per-item sync status (success / invalid / failed) |
integration-acme |
| Webhook entry point authenticated by the platform, not in process code | integration-acme, custom-app-linear |
Activating and protecting webhook / form triggers in metadata.json (webhook.authMode + the workspace webhookAuth, form.authMode, marketplace appRole) |
integration-acme, custom-app-linear |
Multi-step setup form (nextProcessId chaining) |
custom-app-linear |
Dynamic form dropdowns via preRenderProcess + #/variables |
custom-app-linear |
| Creating webhooks + schedules at install, recording them for uninstall | custom-app-linear |
| Polling with a datastore cursor + idempotency (dedup map, or vendor upsert when available) | custom-app-linear |
| Best-effort uninstall / teardown | custom-app-linear |
Storage upload + signed download URL + email with fcode.sendMail |
utility-processes |
| Reading a form-uploaded file from Storage | utility-processes |
Calling the Factorial API SDK (factorial-sdk module) |
all three |
Every fcode App workspace inherits shared modules from the base apps. Import them with fcode.import(...) / fcode.import_module(...); do not reimplement them:
| Module | From | Provides |
|---|---|---|
factorial-sdk |
base-app | createFactorialClient() — authenticated @factorialco/api-client / factorial-api-client instance |
factorial-utils |
base-app | getCompanyId(), setupWebhook(), listWebhookSubscriptions(), deleteWebhookSubscription() |
fcode-forms |
base-app | Form-schema builders: selectField(), toOptions(), … |
mail-helper |
base-app | brandedHtml() for styled email bodies |
error-handler |
base-app | Shared error handling |
outbound-sync |
base-integration-app | OutboundSync base class for marketplace syncs |
Integration apps inherit base-integration-app (which inherits base-app); custom apps inherit base-app directly.
Note: the fcode-forms module above (form-schema builders you fcode.import) is unrelated to the fcode-forms skill, which documents embedding forms on webpages.
The references keep code compact and omit routine logging; real implementations should log verbosely through the shared fcode-logs module (see fcode-javascript / fcode-python).
Every sample exists in JavaScript (Node.js v22) and Python (3.13) with identical structure and behavior. References show JavaScript; the Python variant differs only in idiom (main.py, fcode.importmodule, fcode.sendmail, snake_case) — see fcode-python.