Skip to content

suboss87/FDEOps / skills/fde

Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals before a model acts. Use when they prep a readout, when trust shifts, or they say @fde. Route and run the local fde CLI (or npx --yes fdeops). Never ask them to type commands. Not for ordinary code edits in an unbound repo.

FileKindSize
SKILL.mdskill md11.4 KB
agents/openai.yamlconfig219 B
references/ai.mdmarkdown10.5 KB
references/artifacts.mdmarkdown8.7 KB
references/audit.mdmarkdown5.1 KB
references/board-memo.mdmarkdown5.6 KB
references/build.mdmarkdown4.9 KB
references/business-case.mdmarkdown7.2 KB
references/close.mdmarkdown11.7 KB
references/connect.mdmarkdown1.6 KB
references/dashboard.mdmarkdown3.1 KB
references/debrief.mdmarkdown13.7 KB
references/debug.mdmarkdown3.6 KB
references/demo-prep.mdmarkdown2.5 KB
references/discover.mdmarkdown8.9 KB
references/earn-trust.mdmarkdown5.8 KB
references/encode-pattern.mdmarkdown7.9 KB
references/eval-pack.mdmarkdown6.2 KB
references/fintech.mdmarkdown3.6 KB
references/gov.mdmarkdown3.1 KB
references/healthcare.mdmarkdown2.8 KB
references/hold-scope.mdmarkdown6.8 KB
references/ingest.mdmarkdown6.2 KB
references/integrate.mdmarkdown4.7 KB
references/land.mdmarkdown14.4 KB
references/pick-three.mdmarkdown6.0 KB
references/plan.mdmarkdown15.8 KB
references/poc.mdmarkdown5.9 KB
references/qa.mdmarkdown2.6 KB
references/readout.mdmarkdown6.7 KB
references/record-setup.mdmarkdown1.7 KB
references/record-work.mdmarkdown6.4 KB
references/red-team.mdmarkdown6.5 KB
references/rescue.mdmarkdown7.5 KB
references/review.mdmarkdown5.3 KB
references/rollback.mdmarkdown4.9 KB
references/runbook.mdmarkdown4.5 KB
references/score-use-cases.mdmarkdown6.9 KB
references/ship.mdmarkdown10.6 KB
references/source-setup.mdmarkdown2.8 KB
references/switch-clients.mdmarkdown5.8 KB
references/task-context.mdmarkdown6.6 KB
references/test-assumptions.mdmarkdown7.7 KB
references/three-options.mdmarkdown6.3 KB
references/verification.mdmarkdown5.5 KB
references/what-breaks.mdmarkdown5.3 KB
references/who-decides.mdmarkdown6.7 KB

references/fintech.md

View on GitHub
# fintech overlay - money moves, failures are silent

**Activate when you hear:** payments, transfers, settlements, reconciliation · PCI-DSS, PSD2, SOX, open banking, SWIFT · banking, lending, insurance, trading, crypto · "we handle money" in any form. Loads **alongside** the active phase, never instead of it.

**Read first:** apply [task context](task-context.md). Use permitted data-classification and AI-policy evidence from the supplied brief or existing `trust-profile.md`; use `terrain.md` when reviewing transaction/cardholder code. Resolve missing permissions before the affected action; continue independent analysis using permitted evidence.

Financial systems carry a failure class others don't: **silent money loss.** A bug that processes a payment twice or drops a transaction is regulatory breach + customer harm + potential criminal liability, not a defect ticket.

## The first conversation

> "Does this system store, process, or transmit cardholder data? What's the current PCI-DSS compliance level?"

Cardholder data = PAN, CVV, PIN, expiry. PAN never stored post-authorisation without explicit business case + encryption + masking (last 4 only). **Full PANs in logs, analytics events, or error messages is the first finding and outranks everything else.** Tag all cardholder scope in `trust-profile.md` under `<private>`.

## Idempotency - the most common silent failure

Same operation twice must equal once. Retries, network failures, double-clicks all duplicate requests; without idempotency that's double charges and phantom credits. On any code that creates transactions, verify:
- An idempotency key on every write operation
- Key checked **before** processing, not after
- Retries reuse the same key, never a new one

Missing from a payment flow → flag before production. "We'll add it later" has caused real customer harm in every fintech that said it.

## Transaction integrity

Atomic or nothing. A transfer that debits A and fails before crediting B is a financial error that may require regulatory reporting, not a technical error. Verify: DB-level transactions wrap the operations · compensating transactions exist · **the reconciliation path can catch a discrepancy at midnight.**

## Fraud and reporting - surface early

> "What fraud signals does this system monitor, and what happens when a transaction is flagged?"

Immaturity markers: no velocity checks, no geographic anomaly detection, a review queue nobody actions, a manual override bypassing all controls. The engagement needn't build fraud detection - it must know what exposure the gaps leave. Same for regulatory reporting (CTR/SAR thresholds): manual reporting that relies on memory is a compliance risk; verify changes don't break automated reporting.

## AI in financial systems

Regulators commonly require **explainability** for automated decisions (credit, fraud, account actions). Before any AI-driven decision ships: explainability requirement for this jurisdiction confirmed · right-to-explanation satisfiable · decisions logged with input features. Some institutions prohibit AI final decisions on regulated activities - check `trust-profile.md` first.

## Writes

`trust-profile.md` - cardholder scope, PCI level, AI policy, reporting obligations. `risks.md` - idempotency gaps, integrity issues, fraud-control gaps, compliance exposure.

## Principles

- Idempotency is not optional.
- Full PANs in logs = immediate flag.
- Atomic or nothing; partial transaction states are financial errors.
- If midnight reconciliation can't catch it, there is no financial integrity.
- AI on regulated decisions needs explainability and an audit trail before build.
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall