avem-integration

Name: avem-integration
Author: easyzoom

22stars2forks

How to install avem-integration?

easyzoom/aix-skills/avem-integration

$npx -y skills add easyzoom/aix-skills --skill avem-integration

Installs into the current project.

Summary

Use when integrating, evaluating, configuring, or debugging Avem embedded C framework modules, event-driven components, drivers, middleware, or application architecture

Files · 1

View on GitHub

SKILL.md

1	# Avem Integration
2
3	## Overview
4
5	Use this skill when the user explicitly works with an embedded framework or library named Avem. Because public references can be sparse or project-specific, first confirm the exact repository and then treat Avem as an architecture-level dependency with explicit platform hooks and module boundaries.
6
7	## When To Use
8
9	Use this skill when:
10
11	- The user mentions Avem in an MCU, embedded C, firmware framework, middleware, or application architecture context.
12	- The task involves adapting Avem modules, drivers, event loops, services, or platform hooks.
13	- The user wants to evaluate whether Avem fits a project.
14
15	Do not use this skill when "Avem" refers to an unrelated product, service, or non-embedded codebase.
16
17	## First Questions
18
19	Ask for:
20
21	- Exact Avem repository/source and version.
22	- Target MCU/SoC, RTOS/bare-metal runtime, compiler, and build system.
23	- Which Avem modules are needed.
24	- Required platform hooks: timebase, allocator, logging, storage, drivers, event loop, or RTOS primitives.
25	- Current goal: evaluation, first port, compile fix, runtime bug, or migration.
26
27	## Integration Checklist
28
29	1. Confirm identity and scope.
30	Read the project's own docs/source layout before assuming Avem behavior.
31
32	1. Identify platform hooks.
33	Time, memory, logging, synchronization, drivers, and initialization order must be mapped to the target.
34
35	1. Start with one module.
36	Bring up the smallest useful Avem module before importing the full framework.
37
38	1. Keep boundaries explicit.
39	Application code should not depend on hidden globals or framework internals unnecessarily.
40
41	1. Verify resource impact.
42	Measure flash, RAM, stack, heap, and scheduler impact if Avem becomes a core dependency.
43
44	## Common Failures
45
46	- Assuming Avem's API from another framework with a similar pattern.
47	- Importing the entire framework before one module works.
48	- Platform hooks silently use unavailable malloc, file I/O, or RTOS functions.
49	- Initialization order depends on undocumented global state.
50	- Framework callbacks block timing-sensitive driver paths.
51
52	## Verification
53
54	Before claiming Avem integration works:
55
56	- State the exact Avem source and modules used.
57	- Confirm platform hooks and initialization order.
58	- Confirm one minimal module works on target.
59	- Confirm resource impact or state that it has not been measured.
60	- List assumptions that came from source inspection rather than public docs.
61
62	## Example
63
64	User:
65
66	```text
67	我想把 Avem 接到一个裸机项目里。
68	```
69
70	Agent:
71
72	1. Asks for the exact Avem repository and target platform.
73	1. Identifies required hooks and chooses one minimal module.
74	1. Verifies init, runtime behavior, and resource impact before broader migration.

People who liked this also viewed

6 picks

Type

azure-diagnosticsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deploySkillsJul 2026472k1.3k
systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesSkillsJul 2026197k259k
safe-debugRigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training SkillsMay 2026161k507
explore-runRigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subseSkillsMay 2026161k507
minimal-run-and-auditRigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation SkillsMay 2026161k507
insforge-debugUse when diagnosing problems in an InsForge project — reactive failures (SDK error object, HTTP 4xx/5xx, gateway timeout 502/503/504, edge function failure or timeout, login/OAuth/auth errors, RLS denSkillsJul 202618k31

avem-integration

22stars2forks

View on GitHub

How to install avem-integration?

easyzoom/aix-skills/avem-integration

$npx -y skills add easyzoom/aix-skills --skill avem-integration

Installs into the current project.

Summary

Use when integrating, evaluating, configuring, or debugging Avem embedded C framework modules, event-driven components, drivers, middleware, or application architecture

Files · 1

View on GitHub

SKILL.md

1	# Avem Integration
2
3	## Overview
4
5	Use this skill when the user explicitly works with an embedded framework or library named Avem. Because public references can be sparse or project-specific, first confirm the exact repository and then treat Avem as an architecture-level dependency with explicit platform hooks and module boundaries.
6
7	## When To Use
8
9	Use this skill when:
10
11	- The user mentions Avem in an MCU, embedded C, firmware framework, middleware, or application architecture context.
12	- The task involves adapting Avem modules, drivers, event loops, services, or platform hooks.
13	- The user wants to evaluate whether Avem fits a project.
14
15	Do not use this skill when "Avem" refers to an unrelated product, service, or non-embedded codebase.
16
17	## First Questions
18
19	Ask for:
20
21	- Exact Avem repository/source and version.
22	- Target MCU/SoC, RTOS/bare-metal runtime, compiler, and build system.
23	- Which Avem modules are needed.
24	- Required platform hooks: timebase, allocator, logging, storage, drivers, event loop, or RTOS primitives.
25	- Current goal: evaluation, first port, compile fix, runtime bug, or migration.
26
27	## Integration Checklist
28
29	1. Confirm identity and scope.
30	Read the project's own docs/source layout before assuming Avem behavior.
31
32	1. Identify platform hooks.
33	Time, memory, logging, synchronization, drivers, and initialization order must be mapped to the target.
34
35	1. Start with one module.
36	Bring up the smallest useful Avem module before importing the full framework.
37
38	1. Keep boundaries explicit.
39	Application code should not depend on hidden globals or framework internals unnecessarily.
40
41	1. Verify resource impact.
42	Measure flash, RAM, stack, heap, and scheduler impact if Avem becomes a core dependency.
43
44	## Common Failures
45
46	- Assuming Avem's API from another framework with a similar pattern.
47	- Importing the entire framework before one module works.
48	- Platform hooks silently use unavailable malloc, file I/O, or RTOS functions.
49	- Initialization order depends on undocumented global state.
50	- Framework callbacks block timing-sensitive driver paths.
51
52	## Verification
53
54	Before claiming Avem integration works:
55
56	- State the exact Avem source and modules used.
57	- Confirm platform hooks and initialization order.
58	- Confirm one minimal module works on target.
59	- Confirm resource impact or state that it has not been measured.
60	- List assumptions that came from source inspection rather than public docs.
61
62	## Example
63
64	User:
65
66	```text
67	我想把 Avem 接到一个裸机项目里。
68	```
69
70	Agent:
71
72	1. Asks for the exact Avem repository and target platform.
73	1. Identifies required hooks and chooses one minimal module.
74	1. Verifies init, runtime behavior, and resource impact before broader migration.

People who liked this also viewed

6 picks

Type