flappycode 0.0.0-stage → 1.0.0

package/assets/community-catalog.json

@@ -0,0 +1,26 @@
+{
+  "version": "1.0.0",
+  "updated_at": "2026-10-02T00:00:00Z",
+  "models": {
+    "claude-3-5-sonnet-20241022": {
+      "tier": "paid",
+      "supports_tools": true,
+      "supports_vision": true
+    },
+    "gpt-4o": {
+      "tier": "paid",
+      "supports_tools": true,
+      "supports_vision": true
+    },
+    "gemini-2.0-flash": {
+      "tier": "free",
+      "supports_tools": true,
+      "supports_vision": true
+    },
+    "llama3:8b": {
+      "tier": "free",
+      "supports_tools": true,
+      "supports_vision": false
+    }
+  }
+}

package/assets/rules/categories/backend.md

@@ -0,0 +1,7 @@
+# Category Rules: Backend
+
+1. Input Validation: Validate all incoming payloads using strict schemas (e.g., Zod, Joi, or Pydantic) before executing business logic.
+2. Error Handling: Never expose internal stack traces, DB credentials, or connection strings in HTTP error responses.
+3. Database & Transactions: Use parameterized queries to prevent SQL injection. Wrap multi-table mutations in transactions.
+4. Idempotency & Rate Limiting: Apply rate limiting to authentication and expensive endpoints.
+5. Observability: Structured logging with correlation/request IDs. Redact all tokens and secrets in logs.

package/assets/rules/categories/cli.md

@@ -0,0 +1,6 @@
+# Category Rules: CLI
+
+1. Deterministic Exit Codes: Exit 0 for success, 1 for runtime errors, 2 for CLI argument syntax errors, 130 for SIGINT.
+2. Output Streams: Write program results and primary output to stdout; write diagnostics, progress indicators, and errors to stderr.
+3. Machine-Readable Flags: Support `--json` or `--quiet` for automated scripting environments.
+4. Non-Interactive Grace: Never hang indefinitely waiting for stdin when running non-interactively or in a headless terminal.

package/assets/rules/categories/data-ml.md

@@ -0,0 +1,6 @@
+# Category Rules: Data/ML
+
+1. Determinism & Seeding: Set random seeds explicitly for reproducibility across training, evaluation, and data transformations.
+2. Data Leakage Prevention: Strictly separate training, validation, and test splits prior to fitting feature transformers.
+3. Resource Management: Release GPU memory and batch generators explicitly. Monitor memory consumption.
+4. Schema & Format Validation: Verify data schemas and missing values early in data pipelines.

package/assets/rules/categories/docs.md

@@ -0,0 +1,5 @@
+# Category Rules: Docs
+
+1. Up-to-Date Code Snippets: All code blocks in documentation must match current API contracts and pass linting.
+2. Clear Structure: Single `h1` per page with hierarchical sections. Include a table of contents or quick start where helpful.
+3. Plain Language: Concise, active voice explanations. Avoid jargon without defining terms.

package/assets/rules/categories/frontend.md

@@ -0,0 +1,7 @@
+# Category Rules: Frontend
+
+1. Accessibility & Semantics: Use standard HTML5 landmark elements (`<main>`, `<nav>`, `<header>`, `<article>`). Ensure keyboard navigation and ARIA attributes where appropriate.
+2. State Management: Keep component state local where possible; avoid unnecessary global store pollution.
+3. Performance: Lazy-load non-critical routes and large components. Minimize layout shifts (CLS).
+4. Responsive Design: Mobile-first responsive layouts with CSS grid/flexbox. Do not use hardcoded pixel widths for fluid layouts.
+5. Security: Sanitize all untrusted input; never inject raw HTML without explicit escaping to avoid XSS vulnerabilities.

package/assets/rules/categories/infra.md

@@ -0,0 +1,6 @@
+# Category Rules: Infra
+
+1. Immutability & Reproducibility: Infrastructure code must be declarative and reproducible. Pin base images and package hashes.
+2. Least Privilege: Grant minimum required IAM roles, network ingress rules, and file permissions.
+3. Secret Separation: Never bake API keys or secrets into Docker images or state files; use external secret managers.
+4. Non-Destructive Apply: Require confirmation before running destructive operations (`terraform destroy`, `kubectl delete ns`).

package/assets/rules/categories/library.md

@@ -0,0 +1,6 @@
+# Category Rules: Library
+
+1. Semantic Versioning: Preserve strict public API backward compatibility within major versions.
+2. Minimal Dependencies: Avoid introducing heavy runtime dependencies for trivial utilities.
+3. Dual Module & Types: Provide type definitions (`.d.ts`) and support standard module resolution (ESM / CJS).
+4. No Side Effects: Importing the library must not produce global side effects or mutate standard prototypes.

package/assets/rules/categories/marketing-seo.md

@@ -0,0 +1,5 @@
+# Category Rules: Marketing/SEO
+
+1. Metadata & OpenGraph: Provide unique, descriptive `<title>`, `<meta name="description">`, canonical URLs, and OpenGraph tags (`og:title`, `og:image`, `og:description`).
+2. Performance & Core Web Vitals: Prioritize fast First Contentful Paint (FCP) and low Cumulative Layout Shift (CLS).
+3. Search Crawlers: Maintain valid `robots.txt` and `sitemap.xml` entries. Avoid broken internal links.

package/assets/rules/categories/mobile.md

@@ -0,0 +1,6 @@
+# Category Rules: Mobile
+
+1. Offline Resilience: Handle intermittent network connectivity gracefully with cached data and background sync.
+2. Battery & Memory: Avoid polling loops; release hardware listeners and native bridges when components unmount.
+3. Safe Storage: Store sensitive credentials and tokens exclusively in Keychain / Keystore / SecureStore.
+4. Screen Adaptability: Support multiple device densities, notch insets, and orientation changes.

package/assets/rules/categories/monorepo.md

@@ -0,0 +1,5 @@
+# Category Rules: Monorepo
+
+1. Package Boundaries: Internal cross-package imports must use published or workspace-linked package specifiers, not relative path escapes (`../../`).
+2. Dependency Alignment: Keep shared tooling and common devDependencies aligned across workspace packages.
+3. Isolated Scopes: Package tests and lint tasks must be executable both independently and from the root coordinator.