Skip to main content
Run any Skill in Manus
with one click
augmentcode
GitHub creator profile

augmentcode

Repository-level view of 59 collected skills across 2 GitHub repositories.

skills collected
59
repositories
2
updated
2026-07-14
repository explorer

Repositories and representative skills

core-debugging
software-developers

Inspect runtime state via window.svelteRedux.reduxContext after Store.initDevTool() exposes an initialized Store instance. Multiple exposed stores produce a reduxContext array and a console.error. Use reducer tests for reference-equality diagnostics. Public Store API: @augmentcode/themis/svelte-store; devtools registration is package-internal implementation context.

2026-07-14
core-file-structure
software-developers

Per-slice directory layout ({name}-types.ts, {name}-slice.ts, {name}-selectors.ts, sagas/{name}-saga.ts plus tests). Saga-only slices skip reducer registration. Register reducers in the Store constructor map; store.init() wires the Redux store and package saga manager but does NOT auto-start app sagas โ€” start each one explicitly via store.runSaga(sagaFn). Do not manually register package @internal_ sagas. Ownership: exactly one {name}-slice.ts and one {name}-selectors.ts module per slice directory; split multiple slices into separate directories. Naming: {Feature}State, {feature}Reducer, camelCase slice identity keys/namespaces, verb-phrase actions, select* prefix, "sliceName/actionName" action types.

2026-07-14
core
software-developers

Root routing index for framework-independent Redux and redux-saga guidance in themis. Use for canonical Redux state policy, action/reducer primitives, normalized state helpers, typed-redux-saga patterns, saga manager behavior, saga channel/effect helpers, explicit store pruning, serialization, testing, debugging, and verifier handoff. Use the selected Store family skill for framework-specific Store selector/component behavior, choosing only one concrete Store family per app.

2026-07-14
react-component-integration
software-developers

ReactStore component integration guidance for React app/root wiring. Covers where to create/configure ReactStore, init/dispose ownership, app saga startup with reactStore.runSaga(sagaFn), direct selector signal reads in JSX/TSX, Babel transform/useSignals tracking, selector .useValue(...args) fallbacks for hook/plain-value boundaries, and Store-first dispatch without Svelte or StreamingStore lifecycle rules.

2026-07-14
react-selector-lifecycle
software-developers

React selector lifecycle and call-mode guidance. Maps direct calls that return Preact React signals as the preferred React consumer path, .useValue(...args) for necessary hook/plain-value fallback paths, Babel transform/useSignals tracking, .select(state, ...args) for handlers/tests/composition, .effect(...args) for sagas, and .withStore(...) for explicit binding without Svelte lifecycle rules.

2026-07-14
react-selector-scheduling
software-developers

ReactStore selector emission scheduling guidance. Use for Store-owned coalescing of preferred direct ReadonlySignal outputs and .useValue(...args) fallback reads, throttledSelectorFrequency tuning, package-private scheduler boundaries, and avoiding manual debounce/wrapper subscriptions or audit-log misuse.

2026-07-14
react-selectors
software-developers

Author ReactStore selectors whose direct calls return Preact React ReadonlySignal values and are the preferred React consumer integration path. Covers signal selector arguments, .value tracking via Babel transform or useSignals(), Store-bound creation, .useValue(...args) as a fallback for hook/plain-value boundaries, .withStore(reactStore), pure .select(state) composition/testing, and saga-only .effect() usage without importing React selector internals.

2026-07-14
react
software-developers

ReactStore routing index for React UI work in themis. Use for @augmentcode/themis/react-store, Preact React signals, Babel transform or useSignals() tracking, signal selector results, direct signal reads, selector .useValue(...args) only when hook/plain-value fallbacks are necessary, and React-specific component/lifecycle/scheduling/migration routing. Route shared Redux/redux-saga concepts to core, Svelte readable work to svelte, and Node/server/observable work to streaming. Never mix this concrete React Store family with Svelte Store or StreamingStore patterns in one app.

2026-07-14
Showing top 8 of 58 collected skills in this repository.
Showing 2 of 2 repositories
All repositories loaded