genesis-compiler 1.0.0 → 1.2.0

package/stacks/pieces/java.md

@@ -0,0 +1,22 @@
+# Stack piece: java
+
+## Description
+
+Java package, public type, dependency, lifecycle, and test conventions.
+
+## Requires
+
+- Nothing.
+
+## Indexers
+
+- `java`
+
+## Deslop
+
+- Preserve established packages, public interfaces, dependency injection,
+  lifecycle ownership, checked-error policy, and build-tool conventions.
+- Keep private helpers with their owning class. Consolidate repeated mapping,
+  validation, and resource handling at an existing service or domain boundary.
+- Remove empty facades, single-implementation abstractions, and builder or DTO
+  layers that do not protect a real public or compatibility boundary.

package/stacks/pieces/jskit-mysql.md

@@ -0,0 +1,37 @@
+# Stack piece: jskit-mysql
+
+## Description
+
+JSKIT MySQL runtime, live-schema CRUD generation, and persistence conventions.
+
+## Requires
+
+- `jskit`
+- `mysql`
+
+## Resources
+
+```json genesis-resource
+{
+  "id": "database",
+  "environmentAlternatives": [
+    {
+      "required": ["DATABASE_URL"]
+    },
+    {
+      "required": ["DB_CLIENT", "DB_HOST", "DB_PORT", "DB_NAME", "DB_USER", "DB_PASSWORD"],
+      "allowEmpty": ["DB_PASSWORD"]
+    }
+  ]
+}
+```
+
+## Deslop
+
+- Use the installed JSKIT database runtime and generated resource/repository
+  seams; do not add a second client, connection factory, CRUD transport, or
+  file-persistence fallback.
+- Keep environment normalization, transactions, row mapping, and database
+  error translation at one established persistence boundary.
+- Never compete with or rewrite a generator-owned baseline migration. Preserve
+  retained migration history and data semantics.

package/stacks/pieces/jskit.md

@@ -0,0 +1,70 @@
+# Stack piece: jskit
+
+## Description
+
+JSKIT application creation, package generators, Vue surfaces, app-owned
+generated files, and runtime composition.
+
+## Requires
+
+- `nodejs`
+
+## Skill
+
+- Package: `@jskit-ai/agent-docs`
+- Path: `skills/jskit`
+
+## Guidance
+
+- Before creating or modifying JSKIT Vue/Vuetify UI, load the installed
+  `jskit` Agent Skill and read its `references/material-3.md` completely.
+- Implement Material 3 through JSKIT generators, shared screens, shell and
+  placement seams, app-owned theme configuration, and supported Vuetify APIs.
+- Use geometry-preserving Material skeletons for all user-visible loading;
+  never use a generic spinner or circular progress indicator, or let content
+  jump when data arrives. Actions use stable disabled/pending labels.
+- Keep resource-load and field errors in context, but route transient
+  user-command failures through JSKIT's shared non-layout-shifting action
+  feedback/snackbar path.
+
+## Workspace setup
+
+- Prepare `Install dependencies` with `nodejs` when `package.json` exists: `npm` `install`
+
+## Environment files
+
+- Dotenv `.env`
+
+## Launch
+
+### Target `app`: Run app
+
+- Default.
+- Preferred port: `3000`
+- URL path: `/`
+- Runtimes: `nodejs`
+- Prepare `Build`: `npm` `run` `build`
+- Serve `Start`: `npm` `start`
+
+## Deslop
+
+- For every affected JSKIT screen, load the installed `jskit` Agent Skill,
+  read `references/material-3.md`, and execute its Material 3 audit.
+- Use JSKIT generators, packages, resources, composables, screens, and
+  placement seams instead of parallel framework plumbing.
+- Treat generated output as app-owned and customizable. Adapt routes,
+  placements, and infrastructure tests coherently; when replacing a starter
+  route, update its baseline browser coverage instead of deleting it.
+- Consolidate repeated validation, pending/error state, API access, and page
+  behavior at the generated shared resource or established JSKIT seam.
+- Replace transient command-error alerts that shift page content with the
+  established JSKIT action feedback/snackbar seam; preserve stable in-page
+  resource-load errors, retry states, and field validation.
+- Replace generic in-content spinners with Material skeletons that reserve the
+  final layout, and verify that loading completion does not shift content.
+- Remove pass-through wrappers and abandoned scaffold code only when doing so
+  preserves routes, placements, baseline tests, and observable behavior.
+
+## Commands
+
+- Verify `application`: `npm` `run` `verify`

package/stacks/pieces/kotlin.md

@@ -0,0 +1,22 @@
+# Stack piece: kotlin
+
+## Description
+
+Kotlin package, public callable, coroutine, nullability, build, and test conventions.
+
+## Requires
+
+- Nothing.
+
+## Indexers
+
+- `kotlin`
+
+## Deslop
+
+- Preserve package visibility, nullability, coroutine ownership, public types,
+  dependency injection, and Gradle or multiplatform conventions.
+- Keep private functions near their caller. Consolidate repeated mapping,
+  validation, state, and error translation at an existing boundary.
+- Remove redundant extension functions, wrappers, sealed hierarchies, and
+  generic layers that do not make the domain or lifecycle clearer.

package/stacks/pieces/mysql.md

@@ -0,0 +1,18 @@
+# Stack piece: mysql
+
+## Description
+
+MySQL persistence and migration conventions.
+
+## Requires
+
+- Nothing.
+
+## Deslop
+
+- Keep connection configuration, transaction ownership, and database error
+  translation at one persistence boundary.
+- Use the selected integration's client and migration lifecycle instead of
+  adding parallel connection factories or schema-management code.
+- Preserve migration history and data semantics. Deslop is not permission for
+  destructive schema changes.

package/stacks/pieces/nodejs.md

@@ -0,0 +1,25 @@
+# Stack piece: nodejs
+
+## Description
+
+Node.js package, command, module, dependency, and test conventions.
+
+## Requires
+
+- Nothing.
+
+## Indexers
+
+- `javascript`
+
+## Deslop
+
+- Preserve the package's existing module system, package manager, public
+  exports, registered commands, and supported runtime.
+- Prefer direct modules and Node.js built-ins over wrappers that merely rename
+  an operation.
+- Keep single-consumer helpers private and close to their caller. Consolidate
+  repeated argument, path, serialization, error, and process-lifecycle logic
+  only when one clear shared operation exists.
+- Make subprocess, listener, timer, and cleanup ownership obvious. Remove dead
+  entrypoints and duplicate public exports instead of maintaining aliases.

package/stacks/pieces/php.md

@@ -0,0 +1,23 @@
+# Stack piece: php
+
+## Description
+
+PHP package, namespace, callable, dependency, and test conventions.
+
+## Requires
+
+- Nothing.
+
+## Indexers
+
+- `php`
+
+## Deslop
+
+- Preserve established namespaces, package boundaries, public interfaces,
+  framework lifecycle, dependency injection, and Composer conventions.
+- Keep private and protected helpers close to their owning class. Consolidate
+  repeated request, validation, mapping, and persistence behavior at the
+  existing application seam rather than adding generic utility layers.
+- Remove abandoned service wrappers, duplicated facades, and aliases that do
+  not protect a real compatibility boundary.

package/stacks/pieces/python.md

@@ -0,0 +1,23 @@
+# Stack piece: python
+
+## Description
+
+Python package, module, callable, dependency, and test conventions.
+
+## Requires
+
+- Nothing.
+
+## Indexers
+
+- `python`
+
+## Deslop
+
+- Preserve established package boundaries, public imports, typing style,
+  dependency injection, and synchronous or asynchronous execution conventions.
+- Keep single-consumer helpers private and close to their caller. Consolidate
+  repeated validation, serialization, resource lifetime, and error translation
+  only at one clear existing seam.
+- Remove pass-through modules, speculative base classes, and utility wrappers
+  that merely rename standard Python or framework operations.

package/stacks/pieces/ruby.md

@@ -0,0 +1,22 @@
+# Stack piece: ruby
+
+## Description
+
+Ruby module, class, callable, dependency, lifecycle, and test conventions.
+
+## Requires
+
+- Nothing.
+
+## Indexers
+
+- `ruby`
+
+## Deslop
+
+- Preserve established modules, public entry points, dependency boundaries,
+  lifecycle callbacks, and Bundler and test conventions.
+- Keep private methods with their owning class or module. Consolidate repeated
+  coercion, validation, persistence, and error handling at an existing seam.
+- Remove forwarding objects, metaprogramming, concerns, and service layers that
+  obscure a direct operation without protecting a real shared boundary.

package/stacks/pieces/rust.md

@@ -0,0 +1,22 @@
+# Stack piece: rust
+
+## Description
+
+Rust module, public item, ownership, error, async, Cargo, and test conventions.
+
+## Requires
+
+- Nothing.
+
+## Indexers
+
+- `rust`
+
+## Deslop
+
+- Preserve module visibility, ownership and borrowing, error types, feature
+  gates, async runtime boundaries, and Cargo workspace conventions.
+- Keep private functions near their callers. Consolidate repeated conversion,
+  validation, and resource cleanup only when one ownership model remains clear.
+- Remove needless traits, boxes, clones, wrapper types, and generic layers that
+  do not protect a real semantic or compatibility boundary.

package/stacks/pieces/shell.md

@@ -0,0 +1,23 @@
+# Stack piece: shell
+
+## Description
+
+Shell script function, process, environment, portability, and test conventions.
+
+## Requires
+
+- Nothing.
+
+## Indexers
+
+- `shell`
+
+## Deslop
+
+- Preserve the script's supported shell, command-line contract, environment
+  semantics, quoting rules, exit statuses, and process ownership.
+- Keep private functions close to their callers. Consolidate repeated argument
+  parsing, validation, cleanup, and command execution only at a clear script or
+  sourced-library boundary.
+- Remove needless command wrappers, subshells, pipelines, aliases, and dynamic
+  evaluation that obscure a direct, safely quoted operation.

package/stacks/pieces/vue.md

@@ -0,0 +1,19 @@
+# Stack piece: vue
+
+## Description
+
+Vue component, reactive state, resource hydration, routing, and screen-state conventions.
+
+## Requires
+
+- `nodejs`
+
+## Guidance
+
+### Reactive state hydration
+
+- Cached query/resource data and route state may already exist when a component is created. Never rely on a default lazy `watch()` to initialize writable UI state.
+- Prefer a computed source of truth. When local writable state is necessary, initialize it synchronously and use `{ immediate: true }` for watchers that hydrate or validate from resource data, query results, props, or `route.query`.
+- Keep genuinely change-only watchers non-immediate.
+- Persist user-selected filters and screen context in the URL when they must survive navigation.
+- Test stateful screens by navigating away and back with a warm query cache, including browser back/forward navigation.