prompt examples

This commit is contained in:
Artur Mukhamadiev 2026-08-07 14:57:08 +03:00
parent fa6aca8004
commit 47bb070a1b
4 changed files with 92 additions and 0 deletions

20
appmanager.prompt Normal file
View File

@ -0,0 +1,20 @@
# How Appmanager is working
## Prerequisites
You are sitting in Yocto Root Directory
appmanager recipes might be located in meta-atlas
source code should be found somewhere in ./tmp/work/
binaries in ./tmp/deploy/ipk
## Goal
Investigate in Yocto BitBake repository how Atlas AppManager is working
### Output format
Markdown table with information on basic commands:
launch/stop/list applications

8
chromium.prompt Normal file
View File

@ -0,0 +1,8 @@
You are sitting in chromium fork repository.
Describe to me based on git HEAD commit, which is implementing tabsharing feature.
- How does it work?
- What does it depends on?
- And what is the connected parts?
Start from git check
Provide short report & mermaid flowchart diagram as explainer

40
debug_rpi.prompt Normal file
View File

@ -0,0 +1,40 @@
# Test on remote Rasbperry Pi Zero 2W target
## Prerequisites
Run native-webrtc-viewer via AppManager:
```sh
busctl call com.atlas.AppManager1 /com/atlas/AppManager1 com.atlas.AppManager1 \
Start "s" "com.atlas.app.native-webrtc-viewer"
```
Stop viewer:
```sh
busctl call com.atlas.AppManager1 /com/atlas/AppManager1 com.atlas.AppManager1 \
Stop "s" "com.atlas.app.native-webrtc-viewer"
```
Viewer pid:
ps aux | grep webrtc_viewer | grep -v grep
Viewer logs:
journalctl -u am.com.atlas.app.native-webrtc-viewer.service --no-pager
Remote target:
192.168.0.65
Connect via ssh root@192.168.0.65
## Goal
Measure for 1 minute memory & cpu utilisation using native-webrtc-viewer-testsuite installed on remote target
After finish stop viewer
## Results format
Metric|Minimum | Average | Maximum|
--|--|--|--|
PSS|
CPU Util|

24
feature.prompt Normal file
View File

@ -0,0 +1,24 @@
# Smaps detalisation flag
## Approach
You should follow Test Driven Development on implementation of this feature.
### Requirement
Before reporting on success =>
end2end testing should be performed using tui & cli output formats.
No regression should be detected
If you see any inconsistency - ask me, using question tool. Do not implicitly decide.
If answer to the question could be found using codebase search (only in $PWD) - first research
## Goal
Add --smaps flag with two possible values: VERBOSE|SIMPLE
Default flag value is SIMPLE
When using this value, per producer detalisation on smaps should not be outputted anywhere
On Verbose output -> per producer summary PSS/RSS consumption should be outputted.