What problem does it solve? Developers building features on the appkit-commons framework need consistent patterns for configuration loading, dependency injection, database access, and background scheduling, and mistakes like module-level registry calls or autogenerated Alembic migrations cause subtle runtime failures. ## Core Features & Use Cases - Configuration Management: YAML profiles with environment overrides, nested config auto-registration, and secret resolution via Azure Key Vault or local environment. - Persistence Layer: BaseRepository async CRUD, Entity mixins with auto timestamps, EncryptedString and ArrayType custom columns, and manual Alembic migration conventions. - Scheduling & DI: Service registry singletons plus APScheduler and PGQueuer backends with cron, interval, and calendar triggers for distributed-safe background jobs. - Use Case: When adding a new feature with a database table and a nightly cleanup job, apply this Skill to scaffold the config class, entity, repository, and ScheduledService following framework conventions. ## Quick Start Apply the appkit-commons patterns to add a new feature with a configured service, a database entity with repository, and a scheduled cleanup job.