Mobile logging

Skill ahtishamshahzad/agent_dev_flow/.ai/skills/mobile/mobile-logging

Tool-neutral AI Engineering System: 174 reusable skills (installable as Claude Code plugins) for planning and building software with AI agents. Classify → plan → approve → build under quality gates. Works with Claude Code, Codex, Cursor, Windsurf, Copilot & Antigravity. Canonical in .ai/.

Install

npx -y skills add ahtishamshahzad/agent_dev_flow --skill mobile-logging

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

21 days oldThe repository was created 21 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use to plan logging — structured, level-based logging, dev vs production behavior, and strict exclusion of secrets/PII. Logs aid debugging without leaking sensitive data or bloating production.

SKILL.md

2.9 KB, as published. Nobody here has run it

Mobile Logging

Purpose

Plan logging: structured, level-based logs with different dev/production behavior, and strict exclusion of secrets/PII — useful for debugging without leaking or bloating.

When to Use

When the app needs diagnostic logging or before production hardening.
Not for user-facing error UX (that's mobile-error-handling).

Inputs

Diagnostic needs and log destinations.
Sensitivity of the data involved.

Discovery Questions

What needs logging (events, errors, performance)?
What levels, and how do dev vs production differ?
Where do logs go (console, remote, crash reporter)?
What must never be logged (tokens, PII)?

Responsibilities

Define log levels and a structured format.
Differentiate dev vs production (verbose dev; minimal, safe prod).
Exclude secrets/PII from all logs (../../security-review).
Route logs appropriately (console/remote) without noise.

Required Workflow

Define what/when to log + levels.
Set dev vs production behavior.
Add redaction so no secrets/PII are logged.
Route logs to destinations.
Record the logging plan.

Decision Rules

Never log tokens, passwords, or PII — redact.
Production logging is minimal and safe; verbose logging is dev-only.
Structured, level-based logs over scattered console noise.
Strip debug logs from production paths.

Rules

No secrets/PII in logs, ever.
Different dev vs production verbosity.
Coordinate with error handling + reporting.

Anti-Patterns

Logging tokens/PII.
Verbose console noise in production.
Unstructured, unleveled logs.
Debug logs shipped to production.

Validation Checklist

Levels + structured format defined.
Dev vs production behavior set.
Secrets/PII excluded (redaction).
Destinations routed.
No debug logs in production.

Definition of Done

A recorded logging plan: structured level-based logging, distinct dev/production behavior, PII/secret exclusion, and clean routing — helpful for debugging without leaking or bloating.

Related Skills

mobile-error-handling, ../../security-review, mobile-environment-config

Related Knowledge

../../../knowledge/ (diagnostic needs).

Related References

../../../references/mobile/native/ when populated.

Context Loading Guidance

Requires: diagnostic needs, log destinations, data sensitivity.
Does not require: unrelated screens, the full mobile skill set, unrelated references.
May load: mobile-error-handling, ../../security-review.
Stop when: the logging plan is recorded.

Token Efficiency Guidance

Keep it to levels, dev/prod behavior, and redaction rules.