npm - @bastani/atomic - Versions diffs - 0.6.8 → 0.7.0-2 - Mend

@bastani/atomic 0.6.8 → 0.7.0-2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (765) hide show

package/.agents/skills/bdi-mental-states/references/sparql-competency.md DELETED Viewed

@@ -1,420 +0,0 @@
-# SPARQL Competency Queries
-Validation queries for BDI ontology implementations based on competency questions.
-## Mental Entity Queries
-### CQ1: What are all mental entities?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
-PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
-SELECT DISTINCT ?entity ?type WHERE {
-    ?entity rdf:type ?type .
-    ?type rdfs:subClassOf* bdi:MentalEntity .
-}
-```
-### CQ2: What beliefs does an agent hold?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?belief ?label WHERE {
-    ?agent bdi:hasMentalState ?belief .
-    ?belief a bdi:Belief .
-    OPTIONAL { ?belief rdfs:label ?label }
-}
-```
-### CQ3: What desires does an agent have?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?desire ?label WHERE {
-    ?agent bdi:hasDesire ?desire .
-    ?desire a bdi:Desire .
-    OPTIONAL { ?desire rdfs:label ?label }
-}
-```
-### CQ4: What intentions has an agent committed to?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?intention ?label WHERE {
-    ?agent bdi:hasIntention ?intention .
-    ?intention a bdi:Intention .
-    OPTIONAL { ?intention rdfs:label ?label }
-}
-```
-## Motivational Chain Queries
-### CQ5: What beliefs motivated formation of a given desire?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?belief ?beliefLabel WHERE {
-    ?desire bdi:isMotivatedBy ?belief .
-    ?belief a bdi:Belief .
-    OPTIONAL { ?belief rdfs:label ?beliefLabel }
-}
-```
-### CQ6: Which desire does a particular intention fulfill?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?desire ?desireLabel WHERE {
-    ?intention bdi:fulfils ?desire .
-    ?desire a bdi:Desire .
-    OPTIONAL { ?desire rdfs:label ?desireLabel }
-}
-```
-### CQ7: What beliefs support a given intention?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?belief ?label WHERE {
-    ?intention bdi:isSupportedBy ?belief .
-    ?belief a bdi:Belief .
-    OPTIONAL { ?belief rdfs:label ?label }
-}
-```
-### CQ8: Trace complete cognitive chain for an intention
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?intention ?desire ?belief ?worldState WHERE {
-    ?intention a bdi:Intention ;
-               bdi:fulfils ?desire ;
-               bdi:isSupportedBy ?belief .
-    ?desire bdi:isMotivatedBy ?belief .
-    ?belief bdi:refersTo ?worldState .
-}
-```
-## Mental Process Queries
-### CQ9: Which mental process generated a belief?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?process ?processType WHERE {
-    ?process bdi:generates ?belief .
-    ?belief a bdi:Belief .
-    ?process a ?processType .
-    FILTER(?processType != owl:NamedIndividual)
-}
-```
-### CQ10: What triggered a mental process?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?process ?trigger ?triggerType WHERE {
-    ?process a bdi:MentalProcess ;
-             bdi:isTriggeredBy ?trigger .
-    ?trigger a ?triggerType .
-}
-```
-### CQ11: What did a mental process reason upon?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?process ?input WHERE {
-    ?process a bdi:MentalProcess ;
-             bdi:reasonsUpon ?input .
-}
-```
-## Plan and Goal Queries
-### CQ12: What plan does an intention specify?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?intention ?plan ?goal WHERE {
-    ?intention bdi:specifies ?plan .
-    ?plan a bdi:Plan ;
-          bdi:addresses ?goal .
-}
-```
-### CQ13: What is the ordered sequence of tasks in a plan?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?plan ?task ?nextTask WHERE {
-    ?plan a bdi:Plan ;
-          bdi:hasComponent ?task .
-    OPTIONAL { ?task bdi:precedes ?nextTask }
-}
-ORDER BY ?task
-```
-### CQ14: What is the first and last task of a plan?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?plan ?firstTask ?lastTask WHERE {
-    ?plan a bdi:Plan ;
-          bdi:beginsWith ?firstTask ;
-          bdi:endsWith ?lastTask .
-}
-```
-### CQ15: Which actions executed which tasks?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?action ?task ?time WHERE {
-    ?action bdi:isExecutionOf ?task ;
-            bdi:atTime ?time .
-}
-ORDER BY ?time
-```
-## Temporal Queries
-### CQ16: What mental states are valid at a specific time?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
-SELECT ?mentalState ?type WHERE {
-    ?mentalState bdi:hasValidity ?interval .
-    ?interval bdi:hasStartTime ?start ;
-              bdi:hasEndTime ?end .
-    ?mentalState a ?type .
-    FILTER(?start <= "2026-01-04T10:00:00"^^xsd:dateTime &&
-           ?end >= "2026-01-04T10:00:00"^^xsd:dateTime)
-}
-```
-### CQ17: When was a belief formed?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?belief ?formationTime WHERE {
-    ?process bdi:generates ?belief ;
-             bdi:atTime ?formationTime .
-    ?belief a bdi:Belief .
-}
-```
-### CQ18: What is the temporal validity of an intention?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?intention ?start ?end WHERE {
-    ?intention a bdi:Intention ;
-               bdi:hasValidity ?interval .
-    ?interval bdi:hasStartTime ?start ;
-              bdi:hasEndTime ?end .
-}
-```
-## Justification Queries
-### CQ19: What justifies a belief?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?belief ?justification ?justLabel WHERE {
-    ?belief a bdi:Belief ;
-            bdi:isJustifiedBy ?justification .
-    OPTIONAL { ?justification rdfs:label ?justLabel }
-}
-```
-### CQ20: What justifies an intention?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?intention ?justification ?justLabel WHERE {
-    ?intention a bdi:Intention ;
-               bdi:isJustifiedBy ?justification .
-    OPTIONAL { ?justification rdfs:label ?justLabel }
-}
-```
-## Compositional Queries
-### CQ21: What parts comprise a complex belief?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?belief ?part ?partLabel WHERE {
-    ?belief a bdi:Belief ;
-            bdi:hasPart ?part .
-    OPTIONAL { ?part rdfs:label ?partLabel }
-}
-```
-### CQ22: Find composite mental entities
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?composite (COUNT(?part) AS ?partCount) WHERE {
-    ?composite bdi:hasPart ?part .
-}
-GROUP BY ?composite
-HAVING (COUNT(?part) > 1)
-```
-## World State Queries
-### CQ23: What world state does a belief refer to?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?belief ?worldState ?wsComment WHERE {
-    ?belief a bdi:Belief ;
-            bdi:refersTo ?worldState .
-    OPTIONAL { ?worldState rdfs:comment ?wsComment }
-}
-```
-### CQ24: What actions brought about a world state?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?action ?worldState WHERE {
-    ?action bdi:bringsAbout ?worldState .
-    ?worldState a bdi:WorldState .
-}
-```
-### CQ25: What world states has an agent perceived?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?agent ?worldState ?time WHERE {
-    ?agent bdi:perceives ?worldState .
-    OPTIONAL { ?worldState bdi:atTime ?time }
-}
-```
-## Validation Queries (OWLUnit Style)
-### V1: Every intention must fulfill exactly one desire
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?intention WHERE {
-    ?intention a bdi:Intention .
-    FILTER NOT EXISTS { ?intention bdi:fulfils ?desire }
-}
-# Expected: Empty result set
-```
-### V2: Every belief must reference a world state
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?belief WHERE {
-    ?belief a bdi:Belief .
-    FILTER NOT EXISTS { ?belief bdi:refersTo ?worldState }
-}
-# Expected: Empty result set (or only abstract beliefs)
-```
-### V3: Mental processes must reason upon something
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?process WHERE {
-    ?process a bdi:MentalProcess .
-    FILTER NOT EXISTS { ?process bdi:reasonsUpon ?input }
-}
-# Expected: Empty result set
-```
-### V4: BeliefProcess must generate only Beliefs
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?process ?generated WHERE {
-    ?process a bdi:BeliefProcess ;
-             bdi:generates ?generated .
-    FILTER NOT EXISTS { ?generated a bdi:Belief }
-}
-# Expected: Empty result set
-```
-### V5: Plans must have begin and end tasks
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?plan WHERE {
-    ?plan a bdi:Plan .
-    FILTER NOT EXISTS {
-        ?plan bdi:beginsWith ?first ;
-              bdi:endsWith ?last
-    }
-}
-# Expected: Empty result set
-```
-## Multi-Agent Queries
-### CQ26: What beliefs are shared across agents?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?belief (COUNT(DISTINCT ?agent) AS ?agentCount) WHERE {
-    ?agent bdi:hasMentalState ?belief .
-    ?belief a bdi:Belief .
-}
-GROUP BY ?belief
-HAVING (COUNT(DISTINCT ?agent) > 1)
-```
-### CQ27: Which agents share the same desire?
-```sparql
-PREFIX bdi: <https://w3id.org/fossr/ontology/bdi/>
-SELECT ?desire ?agent1 ?agent2 WHERE {
-    ?agent1 bdi:hasDesire ?desire .
-    ?agent2 bdi:hasDesire ?desire .
-    FILTER(?agent1 != ?agent2)
-}
-```

package/.agents/skills/bun/SKILL.md DELETED Viewed

@@ -1,233 +0,0 @@
----
-name: Bun
-description: Use when building, testing, and deploying JavaScript/TypeScript applications. Reach for Bun when you need to run scripts, manage dependencies, bundle code, or test applications with a single unified tool.
-metadata:
-    provider: atomic
-    mintlify-proj: bun
-    version: "1.0"
-    internal: true
----
-# Bun Skill Reference
-## Product Summary
-Bun is a unified JavaScript runtime, package manager, bundler, and test runner written in Zig. It replaces Node.js, npm, esbuild, and Jest with a single fast binary. Key files: `bunfig.toml` (configuration), `bun.lock` (lockfile), `package.json` (project metadata). Primary commands: `bun run`, `bun install`, `bun build`, `bun test`. Bun is 4x faster than Node.js on startup and 25x faster than npm for installations. Visit https://bun.com/docs for comprehensive documentation.
-## When to Use
-Use Bun when:
-- **Running scripts**: Execute TypeScript/JavaScript files directly without compilation steps (`bun run file.ts`)
-- **Managing dependencies**: Install, add, remove, or update packages faster than npm/yarn/pnpm (`bun install`, `bun add`)
-- **Bundling code**: Build JavaScript/TypeScript for browser or server targets with `bun build`
-- **Testing**: Run Jest-compatible tests with built-in test runner (`bun test`)
-- **Building full-stack apps**: Bundle server and client code together into single executables
-- **Monorepo workflows**: Use workspaces and filtering to manage multiple packages
-- **Replacing Node.js**: Run any Node.js-compatible code with better performance
-Do not use Bun for: type checking (use `tsc` separately), generating type declarations, or projects requiring exact Node.js compatibility for native modules.
-## Quick Reference
-### Essential Commands
-| Task                 | Command                                    | Notes                                              |
-| -------------------- | ------------------------------------------ | -------------------------------------------------- |
-| Run TypeScript file  | `bun run file.ts`                          | Transpiles on-the-fly; omit `run` for short form   |
-| Run package script   | `bun run dev`                              | Executes script from `package.json`                |
-| Install dependencies | `bun install`                              | Creates `bun.lock` lockfile                        |
-| Add package          | `bun add react`                            | Adds to `dependencies`; use `-d` for dev           |
-| Remove package       | `bun remove react`                         | Removes from `package.json` and `node_modules`     |
-| Run tests            | `bun test`                                 | Finds `*.test.ts`, `*.spec.ts` files automatically |
-| Build bundle         | `bun build ./src/index.ts --outdir ./dist` | Bundles with tree-shaking, minification optional   |
-| Watch mode           | `bun --watch run file.ts`                  | Re-runs on file changes                            |
-| Create project       | `bun init`                                 | Scaffolds new project with templates               |
-### Configuration File: bunfig.toml
-Located at project root or `~/.bunfig.toml` (global). Optional but useful for customization.
-```toml
-[install]
-dev = true                    # Install devDependencies
-optional = true               # Install optionalDependencies
-peer = true                   # Install peerDependencies
-linker = "hoisted"           # "hoisted" or "isolated" (pnpm-style)
-saveTextLockfile = true      # Use text bun.lock instead of binary
-[serve]
-port = 3000                  # Default port for Bun.serve()
-[test]
-root = "."                   # Test root directory
-coverage = false             # Enable coverage reporting
-timeout = 5000               # Per-test timeout in ms
-preload = ["./setup.ts"]     # Scripts to run before tests
-[run]
-shell = "system"             # "system" or "bun" (Windows defaults to "bun")
-bun = true                   # Auto-alias node to bun in scripts
-```
-### File Types Supported
-Bun natively handles: `.js`, `.jsx`, `.ts`, `.tsx`, `.json`, `.jsonc`, `.toml`, `.yaml`, `.html`, `.css`, `.wasm`, `.node`. No configuration needed—just import and use.
-### Key Bun APIs
-| API              | Purpose           | Example                                     |
-| ---------------- | ----------------- | ------------------------------------------- |
-| `Bun.serve()`    | Start HTTP server | `Bun.serve({ port: 3000, fetch: handler })` |
-| `Bun.file()`     | Read/write files  | `await Bun.file("path.txt").text()`         |
-| `Bun.write()`    | Write to disk     | `await Bun.write("out.txt", data)`          |
-| `Bun.build()`    | Bundle code       | `await Bun.build({ entrypoints, outdir })`  |
-| `Bun.Transpiler` | Transpile code    | `new Bun.Transpiler({ loader: "tsx" })`     |
-| `Bun.spawn()`    | Run child process | `Bun.spawn(["ls", "-la"])`                  |
-## Decision Guidance
-### When to Use Hoisted vs Isolated Linker
-| Scenario                      | Use        | Reason                                            |
-| ----------------------------- | ---------- | ------------------------------------------------- |
-| New monorepo/workspaces       | `isolated` | Prevents phantom dependencies, stricter isolation |
-| New single-package project    | `hoisted`  | Traditional npm behavior, simpler                 |
-| Existing project (pre-v1.3.2) | `hoisted`  | Backward compatibility                            |
-| Migrating from pnpm           | `isolated` | Matches pnpm's approach                           |
-Set in `bunfig.toml`: `linker = "isolated"` or via CLI: `bun install --linker isolated`
-### When to Use bun build vs bun run
-| Use Case                    | Tool                      | Why                                  |
-| --------------------------- | ------------------------- | ------------------------------------ |
-| Execute TypeScript directly | `bun run`                 | Fast transpilation, no output files  |
-| Prepare for production      | `bun build`               | Minification, tree-shaking, bundling |
-| Ship single executable      | `bun build --compile`     | Creates standalone binary            |
-| Development server          | `bun run` + `Bun.serve()` | Hot reload, fast iteration           |
-### When to Use --concurrent in Tests
-| Scenario                | Use `--concurrent` | Reason                                        |
-| ----------------------- | ------------------ | --------------------------------------------- |
-| Independent async tests | Yes                | Parallel execution speeds up suite            |
-| Tests with shared state | No                 | Use `test.serial()` for order-dependent tests |
-| Database/API tests      | Maybe              | Only if tests don't interfere                 |
-| Unit tests              | Yes                | Usually safe and faster                       |
-## Workflow
-### 1. Initialize a Project
-```bash
-bun init my-app
-cd my-app
-```
-Choose template: Blank, React, or Library. Creates `package.json`, `tsconfig.json`, `.gitignore`.
-### 2. Install Dependencies
-```bash
-bun install
-```
-Reads `package.json`, downloads packages, creates `bun.lock`. Much faster than npm.
-### 3. Add Packages
-```bash
-bun add react
-bun add -d @types/react typescript
-```
-Updates `package.json` and `bun.lock` automatically.
-### 4. Write and Run Code
-```bash
-# Create index.ts
-echo "console.log('Hello Bun!')" > index.ts
-# Run it
-bun run index.ts
-```
-Bun transpiles TypeScript on-the-fly; no build step needed.
-### 5. Create HTTP Server
-```typescript
-// server.ts
-const server = Bun.serve({
-  port: 3000,
-  fetch(req) {
-    return new Response("Hello!");
-  },
-});
-console.log(`Listening on ${server.url}`);
-```
-```bash
-bun run server.ts
-```
-### 6. Write Tests
-```typescript
-// math.test.ts
-import { test, expect } from "bun:test";
-test("2 + 2 = 4", () => {
-  expect(2 + 2).toBe(4);
-});
-```
-```bash
-bun test
-```
-Finds and runs all `*.test.ts` files automatically.
-### 7. Bundle for Production
-```bash
-bun build ./src/index.ts --outdir ./dist --minify
-```
-Outputs optimized bundle to `dist/`. Use `--target browser|node|bun` to control output format.
-### 8. Create Standalone Executable
-```bash
-bun build ./cli.ts --outfile mycli --compile
-./mycli
-```
-Bundles code + Bun runtime into single executable; no dependencies needed.
-## Common Gotchas
-- **Lifecycle scripts disabled by default**: Bun doesn't run `postinstall` scripts for security. Add trusted packages to `trustedDependencies` in `package.json` to allow them.
-- **`bun run` vs `bun <script>`**: If a built-in Bun command exists with the same name, use `bun run <script>` explicitly to run package.json scripts.
-- **Watch mode flag placement**: Use `bun --watch run file.ts`, not `bun run file.ts --watch`. Flags after the filename are passed to the script itself.
-- **TypeScript errors on Bun global**: Install `@types/bun` and add `"lib": ["ESNext"]` to `tsconfig.json` compilerOptions.
-- **Lockfile format**: Bun v1.2+ uses text `bun.lock` by default (not binary `bun.lockb`). Commit to version control.
-- **Auto-install disabled in CI**: Set `install.auto = "disable"` in `bunfig.toml` for production to prevent unexpected package downloads.
-- **Node.js compatibility**: Bun implements most Node.js APIs but not all. Check docs for `node:` module support before relying on Node-specific code.
-- **Bundler always bundles**: Unlike esbuild, `bun build` always bundles by default. Use `Bun.Transpiler` to transpile individual files without bundling.
-- **No type checking in bundler**: `bun build` does not type-check. Run `tsc --noEmit` separately for type validation.
-- **Peer dependencies installed by default**: Unlike npm, Bun installs peer dependencies automatically. Set `peer = false` in `bunfig.toml` to disable.
-## Verification Checklist
-Before submitting work with Bun:
-- [ ] Run `bun install` to verify dependencies resolve without errors
-- [ ] Run `bun run <script>` to test main entry point
-- [ ] Run `bun test` and verify all tests pass
-- [ ] Run `bun build` and check output files exist in `outdir`
-- [ ] Verify `bun.lock` is committed to version control (not `.gitignore`d)
-- [ ] Check `bunfig.toml` for any environment-specific settings that should be removed
-- [ ] Confirm no `node_modules` folder is committed (should be in `.gitignore`)
-- [ ] Test with `--production` flag if building for deployment: `bun install --production`
-- [ ] Verify TypeScript files have no type errors: `bun run tsc --noEmit` (if tsc installed)
-- [ ] Check that `package.json` `"type": "module"` is set for ESM projects
-## Resources
-**Comprehensive navigation**: https://bun.com/docs/llms.txt — Page-by-page listing of all Bun documentation.
-**Critical pages**:
-1. [Bun Runtime](https://bun.com/docs/runtime) — Execute files, scripts, and manage the runtime
-2. [Package Manager](https://bun.com/docs/pm/cli/install) — Install, add, remove packages and manage dependencies
-3. [Bundler](https://bun.com/docs/bundler) — Bundle JavaScript/TypeScript for production
-4. [Test Runner](https://bun.com/docs/test) — Write and run Jest-compatible tests
-5. [bunfig.toml](https://bun.com/docs/runtime/bunfig) — Configure Bun's behavior
----
-> For additional documentation and navigation, see: https://bun.com/docs/llms.txt